They hype-train on all of this stuff is unreal. React+NextJS+Tailwind+ShadCN is just a mess. It's complexity piled on deeper complexity - for little gain! But suggest any of that in many circles and you'll get the standard, "skill issu bro" comebacks. Say what you want about Remix/ReactRouter 7 (there are plenty of issues to talk about there) but at least those guys _tried_ to stay closer to existing web standards. I could go on and on about the disaster of NextJS caching. I could point out RSCs being one way to solve a problem that could already be solved by loaders in other frameworks....
Tailwind was my moment of saying, "Nope, I'm gonna sit this one out". I have a few trusted friends that assure me I'm missing out. I've told them to come back to me after they've done their first major refactor. If they tell me it was a pleasant experience, I'll have another look.
AirBnB doesn't use this config and you probably shouldn't either. Much of this was based on Jordan Harband's opinions in 2016. He's likely changed his mind since then. Perhaps not. But I bet he'd tell you to do your own profiling and consider your own targets before blindly accepting a one-size-fits-all configuration for your linter.
This was added to the language 10 years ago. So while it's "newer" than a plain old for-loop, it's definitely not "new". It was designed to work with Symbol.iterator. This is the mechanism whereby one can iterate anything that implements the Symbol.iterator interface.
As far as why folks won't just do simple for-loops, it's the same reasining every language tends to implement a "foreach", because there are annoying off-by-one errors lurking in the < vs <=. Of course one could argue that developers should be smart enough to handle this. But that's an argument even older than for-loops.
I can give an anecdote if that's helpful. Imagine you're wanting to download an object from S3. You start to type out the command in your CLI. You hit enter, only to realize, see that the object is not found. You have a typo somewhere... but where? The bucket is huge so, you resort to listing the contents and passing the results through grep. Then you copy the object to the clipboard so that you can edit your original command.
I see one of the other comments mentions K9s. The exact same use cases manifest with that tool. YES, if it's just a one-shot, nothing beats the CLI. Many things where you need to investigate the resources a bit more, lend themselves to a TUI (or GUI if that's your thing).
I come from an era where folks could fly through tasks on dumb terminals. (AS/400 apps). The moment we gave them "better" gui tools, they slowed way down. No matter how many times we told them, "you can still use your TAB and ENTER keys!" TUIs were just a sweet spot.
I don't want to pile on you as I see you've already taken a hit - so I'll leave the voting out of this. But consider how many people you knew in the 80s/90s with a Laser Disc player. It was very niche. You likely had one techy nerd friend, or you had a friend that had a dad that was always buying "the next big thing". I think I knew ONE GUY that bought a laser disc player. Contrast that with just Tesla (not even EVs). You likely know 4 or 5 friends or family that own one. The model Y was the best selling vehicle last year. Whether that trend lasts into the 2050s, none of us can know. But calling it a failure? I just don't see it.
And of those things we've been told, a high percentage of them have had to do with battery technology. Science is full of discoveries, science at scale doesn't always work out like we've hoped.
In our org, an RFC precedes a tech spec. The RFC literally is the "let's formally talk about this before we nail down a specification". For smaller specs, annotated comments can serve this purpose. Before this process, what we had found was no one was paying attention to tech discussions in our eng slack channels. Having an RFC gave us an inflection point where we could point back and say, "an official discussion happened, we decided to move forward with a spec".
Perhaps. Watching my GenZ kids react to AI commercials during the Macy's Thanksgiving Day parade, there was general revulsion. It seems many of them are seeking authenticity not uncanny. I know this would be an anathema in a board room where the cost of producing an amazing commercial via AI would make a C-suite sparkle with delight. No paid actors? No sound stage? No reshoots?
And yet, my kids reject it. It's odd. This is coming from a guy who loved watching frogs belch out the name of a beer company in the 90s....
CA Clipper database stuff was my jam! I only wish I had gotten into Turbo Vision. I used to watch my users fly through db apps filling out forms, hititng TAB between fields. There was just something so natural about it. The first app we ported to a web-based solution was really painful to watch.
Taking a guess here but, I think what they're saying is, if most investors have gone all-in on AI, and the bubble pops, who will be investing in the next big thing? What investors will still have money to invest?
Most deadlines are completely made up to create a false scarcity of time. While I agree this one is pretty meaningless and we'll forget about it in a few days... it's not unlike any other silly deadline.
Looking at the landscape around me, no. Everyone is in crisis cost-cutting, "gotta show that same growth the C-suite saw during Covid" mode. So being multi-provider, and even in some cases, being multi-regional, is now off the table. It's sad because the product really suffers. But hey, "growth".
I'm on that same journey. 8 months ago, I was sitting at my desk and all of a sudden my left ear just went out. The ringing was there. I figured the same that it was wax. I've always had wax issues with that ear that require a doctor's office visit. (trying the home kits has only made it worse!) But this time the doctor came in, looked in the ear and said, "there's no wax at all in that ear". What followed sounds much like your journey. Visits to ENT, CT Scans - waiting on an MRI to ensure there's no tumor... All the while I went from having great hearing to having to say, "say that again" all the time.
I had high hopes for Kylix back around the turn of the millennium. At that time my company was looking moving an organization with field agents to a full Linux-based system. Our options were: 1. Keep the existing CA Clipper accounts receivable/accounts payable apps and run on emulated DOS. 2. Attempt to leverage the Harbour language (CA Clipper compatible web based thing). 3. Rewrite the system in Delphi/Kylix. We actually got fairly far with Kylix and I'll always be a fan of Delphi. In the end a pure web-based rewrite won over all those original options. I feel bad for whomever took over that old PHP4 stuff!
For reference, I did use Magit for my short stint with Emacs (and then Spacemacs/Doom Emacs). I've always been more into Vim. I tried the Atom editor several years ago with lots of Vim emulation and quite a bit of customization - one of those being a Magit clone.
I moved to NeoVim many years ago and have been using NeoGit (a supposed Magit clone) the entire time. It's good but I'm missing the "mind blowing" part. I'd love to learn more though! What features are you using that you consider amazing?
Even though I do not write Elixir on the job, I often cite their docs as a gold standard. They're succinct, easy to read, and most often show an example of how a method is used. What's better is that the language has documentation as a first-class citizen (it's even testable!) meaning your auto-generated docs will look as nice as the language's.
I complain about OCaml docs all the time. But Elixir? no way.
I remember about 5 years ago, StackOverflow for OCaml was a nightmare. It was a mishmash of Core (from Jane Street) Batteries, and raw OCaml. New developers were confronted with the prospect of opening multiple libraries with the same functionality. (not the correct way of solving any problem)
I think you're referring to OxCaml. I'd love to see this make a huge splash. Right now one of the biggest shortcomings of OCaml, is one is still stuck implementing so much stuff from scratch. Languages like Rust, Go and Java have HUGE ecosystems. OCaml is just as old (even older than Rust since OCaml inspired Rust and its original compiler was written in OCaml) as these languages. Since it's not been as popular, it's hard to find well-supported libraries.
If I had to simply bind to a native toolkit, I think Lazrus can do that. Having loved Delphi back in the day, I think I'd prefer to write ObjectPascal for anything more than a very simple utility. C# would likely be my second choice.
Good luck debugging and fixing the multitude of errors introduced by your LLM. ESPECIALLY if you're outputting some low-level assembler or machine code. At least when we have our AI outputting Java/Typescript/Python/etc, it's easy (for a programmer) to see where it's run afoul.
This is what's making me laugh a bit about Ford's brazen "we're firing all the white-collar workers" nonsense. Ok, go for it. Who are you going to get to buy a $80,000 F-150?
To whom does one sell when they've deleted their workforce? Seeing company after company add to unemployed workers shows they have no forward-thinking ecomonomists advising them. Further, AI for all of its positive potential is NOT going to be free... or even "cheap" once the investors dry up.
Oracle is exactly who sprang to mind. Throughout my history as a software developer, even Microsoft has had a ton of interest in being involved in the community. Yes, they've wanted to extinguish much of it, when it didn't align with their financial goals... but they were always interested in being part of the "software development conversation". Oracle on the other hand has never extended an olive branch. They're quite happy existing on their own proprietary island. A great reminder that, "they don't want ot play in the pool with you, they want to own the whole pool and charge you to swim in it".
As a Vim user, and a 65% keyboard user with my ESC key mapped to `~`, I found out early on that using ESC in Vim is better relegated to CTRL+[ or `jk` (when in insert mode). Fortunately, that stupid touchbar didn't slow me down as much as others have mentioned. The volume control (that would get stuck) on the other hand...
For a look at some of the amazing output from an "ancient" EOS, you can look at Magic Lantern's Discord. It's rather shocking how far this little camera could be pushed. It is definitely a fun hobby project to fool around with these things. After awhile I stopped having the time and moved over to Sony APS-C with vintage lenses. I was able to maintain some of the aesthetic without getting frustrated by stuttering video. Still it's really a cool project.
We do React Router 7 (previously Remix) with Fastify for a couple of our apps. Both external and internal. I'm really happy with the dev experience. We also have plenty of NextJS floating around here too. Most teams use it as a "better Create React App". There's little use of any of its features. I'm the only one that's used any server-side stuff.
For my team, React Router 7 just gets out of the way. If you use it in framework mode (SSR) you will have loaders and actions, which are things that run on your server. I find it SO much less convoluted. The logger example from the article above is childs play in React Router. Either import your logger and run it in your loader. (You may want to add .server.ts to make it explicitly ONLY server) or inject the logger via context.
I had a project slated to use this framework. The pilot went fairly well. Fresh has the right ideas on static vs dynamic islands. In the end, we deployed with Astro - which also has similar ideas. In the end, I just wasn't able to get full buy-in on Deno.