IMO Bun and Vite are best suited for slightly different things. Not to say that there isn't a lot of overlap, but if you don't need many of the features Bun provides, it can be a bit overkill.
Personally, I write a lot of Vue, so using a "first party" environment has a lot of advantages for me. Perhaps if you are a React developer, the swap might be even more straightforward.
I also think it's important to take into consideration the other two packages mentioned in this post (oxlint & oxfmt) because they are first class citizens in Vite (and soon to be Vite+). Bun might be a _technically_ faster dev server, but if your other tools are still slow, that might be a moot point.
Also, Typescript also "just works" in Vite as well. I have a project on work that is using `.ts` files without even an `tsconfig` file in the project.
One day I'm gonna build some sort of product in Elixir. I was super interested in LiveView when it was announced and I think the component story has gotten a lot better than when I tried back in pre-1.0 days.
Is it possible that there could be two separate things going on here? Anecdotally, I can confirm that my memory when actively using it not better. If you tell me something when I'm zoned out, unless I set a reminder or something in my calendar, fat chance I'll remember the next day. However, I am more of a "occasional weekend" user and then only in the evening after my work and family obligations are taken care of for the day; very similar to how many people consume a whisky or other hard liquor in moderation.
I kinda saw this happen in realtime on reddit yesterday. Someone asked for advice on how to deal with a team that was in over their heads shipping slop. The crux of their question was fair, but they used a different LLM to translate their original thoughts from their native language into English. The prompt was "translate this to english for a reddit post" - nothing else.
The LLM adding a bunch of extra formatting to add emphasis and structure to what might have originally been a bit of a ramble, but obviously human written. The comments absolutely lambasted this OP for being a hypocrite complaining about their team using AI, but then seeing little problem with posting what is obviously an AI generated question because the OP didn't deem their English skills good enough to ask the question directly.
I'm not going to pass judgement on this scenario, but I did think the entire encounter was a "fun" anecdote in addition to your comments.
I saw the same post and was a bit saddened that all the comments seemed to be focused on the implied hypocrisy of the OP instead of addressing the original concern.
As someone that’s a bit of a fence-sitter on the matter of AI, I feel that using it in the way that OP did is one of the less harmful or intrusive uses.
I see it as worse because you could have put just as much effort in - less even - and gotten a better result just sticking it in a machine translator and pasting that.
In western europe today, I spend €10+ per day to heat my home (17 degrees mind you) with a gas powered boiler for radiators. I can run my mini-split on 18 degrees all day for a couple of euros. I moved here from the US in 2022 right after the full scale invasion of Ukraine so natural gas prices skyrocketed overnight.
I don't really understand what the aversion is to forced air climate control here other than "it's not as comfortable" which from what I've gleaned from other people is taken to mean noise/moving air/humidity. Coming from the southern US, I find all of those points to be a non-issue for me. I've slept with a fan on my entire life, so if I can shave off 50% of my heating costs for a few decibels of fan noise, sign me up!
I don't buy your numbers. I'm in Western Europe myself, and have run those numbers multiple times. Kilowatt for kilowatt (COP adjusted) gas is always cheaper than a heat pump.
I would be shocked if this doesn’t exist as a small dongle you could plug into your phone directly or operate wirelessly. If you’re someone who already has a few pieces of EDC, maybe it could be stashed on a keychain.
Are you sure about that? The sustainable operation of modern cars is in doubt, from very specialized parts and fully integrated modules, to critical software that will not be updated, to dealer keying required for most every substitute part, the era of anyone being able to run cars for 200,000 miles long after the warranty is over will soon be in the history books.
I haven't seen any evidence that the "reliable" car brands are trying to change that dynamic moving forward. I think we are seeing a change in consumer behavior that leads to increased demand for new cars, but that is not connected to the reliability of the platform of the long term maintenance requirements.
If electric cars are actually simpler like all of these experts keep telling us, then in the next 3-5 years, we'll know which models are living up to expectations and which ones are not aging as gracefully.
The other thing to consider is the "old" batteries. If I can buy a used Nissan Leaf and harvest the batteries for a home-storage project after the frame kicks the can due to rust or some other problem, then I'm essentially able to keep those batteries as a form of equity on the vehicle. We also will see new companies popping up to address these home-battery conversion projects with plug and play harnesses to drop in your car batteries after the vehicle is no longer worthy of use on the road.
Sure, batteries will also continue to come down in price across the board, so that calculation also needs to be considered, but we're in this interesting middle zone where a lot of used EV value is being left on the table because the business market hasn't quite kept up with the demand for the next step in the lifecycle of modern EVs.
You say this like the average age and reliability of cars hasn't been skyrocketing for years.
Toyota offers a 10-year warranty on new cars, which would have been unthinkable 20 years ago.
You can't update the infotainment, but the engine controls have remained modular because it's simply too hard to convince people to buy truly unrepairable cars. Tesla did it, and once people realized that gently tapping a Model 3 was likely to total it resale values plummeted.
The thing about printf debugging is that it works universally. All languages, all platforms, all stacks. Even down to the lowest levels of most software, there will always be some sort of log available.
While some tools/frameworks might have more robust debugging tools, if you have a dynamic role within an organization, you may not find it worth the effort to set them up if your target platform is constantly changing.
One real world example of this from my own work in PHP - there is a tool/lang-extension called XDebug that is great and provides step through debugging, but historically, it has been a pain to configure. It's gotten better, but when I can just as easily add a few `dump()` statements that expose the same data, it's overkill. Very rarely do I need to actually pause the running request to debug something and 99% of the time, I just want to know the state of that object within an specific `if()` block and a debug log gets me that same information.
I do find this frustrating as an IC. I'm lucky to get a COL raise every year, much less 10-15% in a down year. Not to mention the absolute ridiculous explosion of C-Suite pay in comparison to workers. Something has to change if these companies want to continue to be successful long term.
Personally, I write a lot of Vue, so using a "first party" environment has a lot of advantages for me. Perhaps if you are a React developer, the swap might be even more straightforward.
I also think it's important to take into consideration the other two packages mentioned in this post (oxlint & oxfmt) because they are first class citizens in Vite (and soon to be Vite+). Bun might be a _technically_ faster dev server, but if your other tools are still slow, that might be a moot point.
Also, Typescript also "just works" in Vite as well. I have a project on work that is using `.ts` files without even an `tsconfig` file in the project.
https://vite.dev/guide/features#typescript
reply