> It just seems like we're taking the descriptions we have too literally from an era where medical terminology was often metaphorical
And content creators. I hope I am not the only one who took this plague as a true historical event where people 100% started dancing out of nowhere and died dancing because of scary content I consumed at a younger age like "Top 10 Unexplained Cases Of Mass Hysteria"
Apparently the name stuck because some libraries and websites already adopted the term even if there was no Web3 at all. Lol Jack Dorsey's already working on a Web5 that nobody is interested either.
I think that the real Web3 will be mature and developed enough that there will be no need to create a bunch of apps boasting they're on the Web3 nor libraries abstracting Web3 APIs called "web3.js" before the term is even tangible
This is awesome!
Admin panels are fine to me, but honestly this is a much more beautiful and productive approach. Very cool project.
Is an Astro template/integration a possibility? I'd love an editable static site that triggers Netlify builds. I actually have an Astro project on Netlify CMS that I wouldn't mind moving to this.
The way I see it, Deno was built to be an executable, Typescript-first, Web API first and have a robust security model. Bun is built to be an executable and blazingly fast while still learning from some of Deno's hits and misses.
I think it was basically this dude building an LLVM compiler for Porth, which made Porth's creator (Tsoding Daily) uncomfortable because he felt like he was on a race to see who made his own unfinished language better. He says individuals with an "s", so I'm not sure who else he might be talking about, but I remember this LLVM person being the big shocking reason why he initially closed the source code.
As far as I remember, the LLVM dude apologized in a public comment on the same video where Tsoding complained about this, claiming he was closing the LLVM repo and explaining it was just a toy project he made to understand LLVM better that got some attention.
> Microsoft has taken the descriptive naming style all the way down to products
May be more on the "Developer Products" side, but this is exactly how I feel about PowerShell cmdlets... Did PowerShell's developer team dislike Linux's software/package/scripting ecosystem so much that they had to make two-word long capitalized command names a good practice?
Learn as you develop. I've been there, I've felt like I'm constantly switching techs because my app should have the most bleeding edge stuff.. And in the end I always felt overwelmed at the sheer amount of frameworks/libs coming out every year, or at how the larning curve of each tech didn't allow me to actually develop because I couldn't get past the "Researching and trying out tech before marrying a technology" phase.
The thing is: You A) Don't need to learn the newest things if all you want is to create a cool app. And B) Won't get anything from learning about building apps without actually building them.
Maybe you do need to get off HN, but I recommend just browsing HN safely and knowing that there'll be time to learn these new things if you learn them through making cool stuff. If your priority is to make apps, these new frameworks shouldn't bother you so much. You can make a nice app just with Flask.
But I do feel old too. I used to think Angular was the hottest thing.. Now I hardly enjoy it lol but that's because my Angular-married colleagues use very outdated practices, which were "modern" a few years ago.
I still don't get why React Native is so exaggeratedly popular when re-writing code in huge codebases just because it's similar to the React you use in the desktop.. Or just because it's "A single codebase for both platforms". Do people not research into the topic before starting to migrate? People could work with Flutter, which is still cross-platform and outperforms RN in every way possible. It's like having a single Java or Swift codebase for both apps, because it's a well-thought out framework built for mobile natively (On a language capable of compiling to native), not a hacky workaround to have React represent phone UIs (Built on a mixture of languages).
Lol, thought the same when I read "CPython".. Okay? Why not mention stuff like Godot and Monogame? Those are things the OSS-Gaming community are more familiar with. And why not say "The CPython Interpreter"? As if everyone knew what CPython was.
People will complain about literally anything without ever comparing the UI, UX, Speed or Resource Usage of the thing rivaling their favorite app. Everybody should get Min, use it enough time, then make educated opinions instead of hating in web technologies just for the memes.
I had an idea like this for a university design (Not really centered in design, more on design methodology and research) class. At first I thought of designing a fully customizable, plugin-based EMS (Like Moodle), then my teacher told me to try and make it bigger, so I designed an app platform where there's only extensions and the UI is fully yours, kinda like Notion Enhancer [1] or Better Discord [2], but without the base app.
That's the biggest issue I have with these. They're cool and all, but they're starting to get old. I like how they're including a little "SDK for bulding apps in this fake OS", which is a bit new, but I'd be way more invested in something like a HyperTerm-inspired Portfolio Project or UI Library.
Woah, that really sucks. I checked their website some time ago and though they still had momentum.. :( Hope that rewrite people are talking about in the issue replies does happen at some point.
No joke, a few weeks ago a colleague from university shared a few anecdotes about his mentor-coworker-boss at work with me, and it's similar. Every time they broke the production branch and the boss had to change the code or pull out some AWS magic to restore a database, he would give the fixed commits names like "Cgada de [Employee Name]" which roughly translates to "[Employee Name] F*ed Up", since he knew they wouldn't forget it that way.
It's specially cool given that he would always see his employees' f*k-ups as learning opportunities. He would always teach them what went wrong and how to fix it before shaming them in the git history. He always told them he did it to assure they wouldn't forget both the shameful f*k-up + the bit of learning that came along with it. They always laugh it off and understand the boss' intentions. It isn't harsh or anything.