My open source service, lrclib.net, handles approximately 200 requests per second at peak (yes you read that right, it's approximately 12000 requests per minute) on a simple €13 Hetzner cloud server (4 AMD based VCPU, 8GB RAM). I'd love to write a blog post about how I made it possible sometime in the future, but basically, I cheated by using Rust together with SQLite3 and some caching.
I was surprised by the cost of Vercel in that blog post too, which is why I dislike all kinds of serverless/lambda/managed services. For me, having a dozen people subscribing to $1-$2/month sponsorship on GitHub Sponsors is enough to cover all the costs. Even if no one donates, I’d still have no trouble keeping the project running on my own.
It's simple. Human writing is short and to the point (either because they're lazy or want to save the reader's time), yet still manages to capture your attention. AI writing tends to be too elaborate and lacks a sense of "self".
I feel like this article challenges my patience and attention too much, there is really no need to focus on the pros of upgrading here. We reader just want to know how they managed to upgrade at that large scale, challenges they faced and how the solved them. Not to mention any sane tech writers that value their time wouldn't write this much.
>It's simple. Human writing is short and to the point (either because they're lazy or want to save the reader's time), yet still manages to capture your attention. AI writing tends to be too elaborate and lacks a sense of "self".
Corporate (and SEO) writing has always been overly verbose and tried to sound fancy. In fact, this probably is where LLMs learned that style. There's no reliable heuristic to tell human- and AI-writing apart.
There's a lot of worry about people being fooled by AI fakes, but I'm also worried about false positives, people seeing "AI" everywhere.
In fact, this is already happening in the art communities, with accusations flying left and right.
People are too confident in their heuristics. "You are using whole sentences? Bot!" I fear this will make people simplify their writing style to avoid the accussations, which won't really accomplish anything, because AIs already can be prompted to avoid the default word-salad style.
> Not to mention any sane tech writers that value their time wouldn't write this much.
This is a big part of why the tech is so damn corrosive, even in well-meaning use, let alone its lopsided benefits for bad actors.
Even on the “small” and more-private side of life, it’s tempting to use it to e.g. spit out a polished narrative version of your bullet-point summary of your players’ last RPG session, but then do you go cut it back down to something reasonable? No, by that point it’s about as much work as just writing it yourself in the first place. So the somewhat-too-long version stands.
The result is that the temptation to generate writing that wasn’t even worth someone’s time to write—which used to act as a fairly effective filter, even if it could be overcome by money—is enormous. So less and less writing is worth the reader’s time.
As with free long distance calls, sometimes removing friction is mostly bad.
My hypothesis is that long form content generated by LLMs tend to sound like blogspam and press releases because those are exactly the kinds of things they were trained on. Most content generated by humans for public consumption is ANYTHING but succinct.
Their style is much more direct if you just ask them a question or to summarize something. (Although whether the answer is accurate or not is another matter.)
I like this, as the author of LRCGET (which is made with Tauri), I hate debugging something that works on Windows (Microsoft Edge WebView2) but doesn't work well or doesn't work at all on Linux (Webkit2gtk) or macOS.
One of the example is audio playback. Chromium and in turn Edge WebView2 have great support, but make it work in Webkit2gtk is a big pain in the *s. I then decided to switch the audio playback feature to Rust side (using Kira and Symphonia) instead.
Having Chromium bundled eliminates all the pain about inconsistency between webview engines, and using Rust means we don't have to pay for the NodeJS size in our app bundle (plus better performance).
For Tauri, I think something like Servo will fit well as bundled browser engine. Hopefully some day it will happen.
To this point I just want to have a way to block all Musk related news from my doom scrolling time. I just can't see any meaningful value in these news anymore.
I love the idea of Hotwire and I'm already using it in one of my production project. Overall it saved me a lot of time and frustration having to deal with a separate frontend project, and the frustration having to manually manipulate the DOM with JavaScript in traditional MVC project.
However I faced some other new frustration, such as when trying to make a dynamic nested form (similar to cocoon gem) but only with hotwire stack (turbo frame/stream). It is also hard to think of each hotwire controller as a component, you might face some problems when trying to do some nesting.
I think Hotwire will be a perfect fit if you want a traditional websites with a few dynamic, interactive features. If your website is too much app-like, you should consider switching the frontend part to SPA entirely.
At least it is a mile better than the abomination named Electron.
Each Electron app has both Chromium and NodeJS bundled. Tauri only use platform-specific webviews, and Rust is a compiled language with no GC and no runtime.
Yes, it does suck sometimes, but for UI then your frontend framework should work all the same 99% of the time. If your app is related to audio/video playback or you want to use newer features of Web standard such as webGPU, then it will be trickier.
I understand the changes to Gitea pissed the community so much. But at least it appears they are not resorting to a "bait and switch" with the open-source license, and remain committed to retaining the MIT license.
Offering a managed service and paid support seems like a reasonable move to me, and would certainly benefit many small and medium organizations. The profit gained from business could also provide funding for contributors and maintainers.
I like the approach of taking money from corpos to make FOSS stronger. Hard-forking an already MIT licensed project for just another one is really bad for both side.
As a Vietnamese developer currently interested in remote opportunities, I am a little concerned. I hope people like us won't face any discrimination at work due to being thought of as "stealing an American's job".
For what it’s worth, I hold no ill will toward the new hires. I quite like some of them. But it’s obvious what is going, and I know I’m not alone in considering a career change.
My company employs some VN engineers and they’re great. I’m glad your country is building up such an industry instead of relying on only agriculture and tourism for example.
You'd have a hard time finding a educated tech employee who would discriminate against a population based on regional hiring trends. Like yourself, we can all see through the fog and realize that only the employer is benefiting here.
Everyone's gotta feed their families, you're doing the same work we would do, and all else equal, only the pay is different.
My favorite coworkers to speak with day to day are IN team in analogous role. Very amicable,and we all work to make each other secure.
I can't imagine myself using this. One more port open, one more attack vector for those restless bots to scan for vulnerabilities, one more service I need to keep up-to-date. But I understand it would help Linux servers become more approachable, especially people that are switching away from PHP-based shared hosting to a full-featured VPS, don't have much knowledge about servers, and want something similar to cPanel or DirectAdmin.
