yurishimo

In Dallas where I grew up, it wasn’t necessarily rare but it wasn’t a given by any stretch. Maybe 10% of homes the last time I lived there (2022)? The neighborhood also made a difference.

Where I live now in the Netherlands, it feels like 30-40% of private homes have solar and 80%+ of business and government buildings that use more energy during the daylight hours so the payoff is much more realizable.

This definitely plays a huge factor. Even people who get airco for the first time are already beginning with a different mindset. They also tend to run the units very conservatively because they aren’t used to living in an air conditioned space and often find it uncomfortable after a certain point.

I moved to Western Europe from a US state where airco is mandatory. I purchased a split unit here and on the worst summer weeks, it still only cost me €10 to run the unit on its coldest setting for a week (almost continuously since I was using it with a fan to blow cooler air around the rest of the house). Back in the US, I had summer electricity bills of hundreds of dollars every year.

Sure, the weather is a bit more mild here, but there have been heat waves, and I’m definitely an outlier when it comes to usage. But that just goes to show how efficient these new units are!

1. No, they’ve been talking about it for months publicly.

2. Nothing because Vite is OSS and this is something extra on top for managing everything else people usually use on a project.

Did you watch the keynote from the conference today? The conference attended by all the people who you see as great contributors to the Vite project?

They want this. This is good for the ecosystem to maintain funding as a whole.

Vite OSS is getting Rolldown; it will be part of Vite from version 8 onward. Rolldown itself is also 100% OSS.

It entirely depends on the type of application you are building. Boring CRUD app that is rarely updated? Yea, server rendering is probably enough.

But the requirements of "modern" software are always changing. Sure, the static table might be enough, but then some business person says, "It sure would be nice if I could check a little box in the table row or assign this user here..." and now you're adding little JS hacks. Again, not impossible, but at a certain scale, the ability to have infinite access to client driven reactivity becomes a real business empowerment.

Given the interest in the JS working group to add reactive Signals to the core language, I suspect this will only become _more_ prevalent in the future. Maybe it will need less input from frameworks to do the same work and we can move back towards using built-in browser APIs, but the programming model itself works really well (so much so that SwiftUI uses a very similar reactive UI programming model).

Again, I don't disagree with your point, just at a certain scale, it becomes a huge hassle to maintain. If people are going to use these tools and frameworks anyway, it helps the entire web to make them more efficient.

The Vite tooling is also available separately and is fully MIT open source. This "package" does the dirty work of tying the separate OSS packages together into a singular CLI/GUI tool.

Arent buggy? React had to introduce a compiler because the masses only write buggy code. The reason they likely waited so long to do it is because they felt like it was a waste to write software to fix something that theoretically has “no flaws” because it’s “just JavaScript”.

Literally every other JS framework figured this out years and years ago and some over a decade ago. Compilers help to raise the floor for everyone so we don’t need to worry about making a dumb mistake and drastically slowing down our programs. Compilers are the evolution of software.

I think it definitely depends on your vehicle history. Going from an automatic 2004 Camry to a 2022 Model 3 will feel like a massive jump. But from a stick shift tuned golf? Less so…

We all build on top of something. Today’s browser will look like a native platform in another 20 years. Just like assembly does to our point of view today.

PHP is a great example of the convergence of interfaces. Now they have different “PSR” standards for all sorts of things. There is one for HTTP clients, formatting, cache interfaces, etc. As long as your library implements the spec, it will work with everything else and then library authors are free to experiment on the implementation and contribute huge changes to the entire ecosystem when they find a performance breakthrough.

Types seem like a “feature” of mature software. You don’t need to use them all the time, but for the people stuck on legacy systems, having the type system as a tool in their belt can help to reduce business complexity and risk as the platform continues to age because tooling can be built to assert and test code with fewer external dependencies.

It makes sense in some places; buttons, mostly so quickly tapping a button doesn’t zoom or whatever.

I agree that a lot of people are lazy and block text selection sitewide though because it’s easy and makes the PM go away.

For how long and how often does your power go out? Living just across the channel in NL, I don’t know that I’ve ever had my power go out one time in the last 3 years that I’ve lived here.

It also depends somewhat on how much energy you use. I live in the Netherlands where everytime I bring it up, I'm told "that's just not possible, you will never make enough in winter", but these same people have no idea how much energy I use. On a bad day, I use maybe 10kWh and that's running the AC with the thermostat set to 19c overnight and a bit during the day at 22c. I don't have a giant fridge, I don't have any gaming PCs slurping 200W on standby, etc. My baseline usage is around 300-400W to run the old freezer that never turns off (70W), my network equipment, a fan in the garage to prevent moisture buildup, and some lights.

My 1.8kWh system at 20% output covers a great percentage of my baseline usage during the day! I'm probably going to add a small battery so I'm not penalized for sending energy back to the grid, but I'm not gonna need much until my kids get older and want new gadgets. The cool part about modern electronics is that we're generally getting more efficient too with newer tech. If I replace the old freezer, my baseline usage drops 20%+.

I don't disagree with your point that sometimes nature is simply just working too hard against your efforts, but I also wrote all this to say that some people need to really do the math and not rely on "common knowledge". Energy efficiency has come an extremely long way in the past decade and much of what was true when residential solar first started popping off is now outdated.

I have domains on namecheap that are over a decade old. Time means nothing.

If you can’t afford to live on 150k/year even in SF, that’s just poor financial planning…

It’s not like McDonald’s or Target don’t exist in SF. Those workers get paid way less than big tech and somehow they make rent every month. Yea, you might have to commute instead living within walking distance of the campus where you work, but that’s just being a responsible adult imo.

Laying in bed/couch with the phone over your face and arms outstretched. Eventually your arms get tired or a muscle twitches and you drop the phone on your face.

https://knowyourmeme.com/memes/text-in-bed-drop-phone-on-fac...

You can buy them on Aliexpress for $5. YouTube and a cursory google search will give you many many options to choose from for examples and tutorials.

I mean, sure. But we could do all of those same things to Grandma in 2025 as well.

Exactly this. Meat is a huge source of nutrition. Even though in our modern western society, we might not "need" to eat meat, but it's a hearty, plentiful, accessible protein and fat that stores well and can be easily moved and replicated quickly. It's simply much more practical still to keep eating meat in much of the world. I'm not going to go into the arguments about our biology either, but I think it's safe to say that our bodies are also very finely tuned to eat and process organic (from organisms) meat and use it as fuel. Sure, you can feed your cat a vegan diet or whatever and replace all of the vitamins, but there is no denying that the more "natural" way would be to just eat the meat and be done with it.

Many of the arguments for veganism come alongside ideas for better animal welfare, but the two are not mutually exclusive. The only reason we don't eat grandma after she dies is because it's culturally unacceptable. We can apply more respect and reverence to meat production without stopping entirely or pretending that the benefits of eating meat don't exist.

Are there downsides to "just" sending all of the extra energy to ground? I've often wondered why overpowering the grid has been talked about as this huge unsolvable problem.

I understand it's wasteful, of course, but waste in a ecosystem of vast abundance seems like a feature, not a bug.

Maybe they mean with dependencies? There are some bloated libraries out there but because PHP is a dynamic language, the bloat only matters if it’s in your hot path.

But I would say a 20k line PHP app is pretty small… we probably have 20 different 1k+ files in our app. They’re not pretty but they’re still fast enough and they work so I’m not gonna try and rewrite them just for giggles.

That said, when working on this legacy behemoth, it’s not uncommon we find a way to delete a few hundred lines because there are so many old features that aren’t needed by the business anymore so we can remove that cognitive load from codebase. Maybe that had a similar experience and the rewrite was just a good time to get buy in from the business to admit that the features weren’t important anymore. We run an e-commerce site so there are lots of little marketing experiments cluttering the app and it’s a constant churn to remove old ones and add new ones for people to tweak and test with feature flags. Removing dead code is just a part of the job.

Templating languages in PHP are largely about better ergonomics. Sure, you can have your own helper functions that do the html escaping or an abstraction layer to pass variables into includes without polluting global variable scope, but that’s all boilerplate.

Twig and Blade are both fine templating engines with their own quirks and features but they’re also battle tested and have proven their use over the past decade+. If someone wants to use a dedicated templating language for abstracting away chunks of HTML, it’s low on my list of complaints.

As someone who came to Laravel from WordPress, I had a massive hole in my abilities to understand larger systems as a whole. During my tenure in WordPress, I actually got pretty good at the web native parts of modern web development but my “backend” skills were mostly about passing arrays around and doing simple database operations. Basic concepts like MVC were totally foreign to me and I was reminded of this a few months ago when I chatted with an old friend about their experiences with Laravel after the drama in WP land a few months back. When I told him that Models were not anything special and you didn’t need to scaffold out a Model using Laravel to create your own class against an existing table, his mind was blown and I could see the gears starting to turn. Mind you, this is a very successful solopreneur with a thriving theme business/platform and over a decade of experience; just that xp was in a domain set apart from the discipline of modern software engineering.

I’m super happy to have spent that time learning how to work with constraints to build absolutely giant systems (had a stint with an agency that worked for big online publishers that are known for using WP…) but after seeing the other side, I’m also happy to be past that and onto different and more interesting things.

Yea it can be done, but it requires thoughtful implementations and planning if you are working within a mature system.

We had/have a similar problem where things began with "a sprinkle of js here/there" and then over time those islands became much bigger and encompassed more and more functionality. Entire backend templates were ported to the JS framework and then the page with load and then stuff would pop in after the DOMReady event was fired and the JS booted.

I've been working backwards to remove many of these changes and handle them server side if possible or at least give a better UX while the frontend is getting ready. It's not easy!

In a perfect world, we could run the output of the PHP backend through a JS SSR endpoint and hydrate the few necessary components into full HTML, but unfortunately, many of today's JS SSR tools are only available if you use the meta framework as well.

What's going to be fun over the next year is finally deciding if we should go "all-in" on a JS frontend (using Inertia.js for the communication with the backend) or go back to PHP entirely and try to leverage more browser capabilities. There's not really a right/wrong answer but if marketing want's to keep adding flashy features, having the flexibility of JS would be handy.

Really? That's crazy. I'm earning a bit over 5k in the Netherlands. Granted, not Amsterdam, but still.

And what’s worse is that the tariffs are going to bring in real revenue in the near term. Perhaps the government can wait a year before trying to earmark that money, but by the time the next president gets elected, that income will be expected. There is the opportunity to shift the tariffs into certain products (like a wealth based consumer tax - ie a 100% import tariff on your super yacht) but that will take time to work out the details for.

I feel sorry for my American friends and family but at the end of the day, actions have consequences. Wishing them all a speedy recovery!

So, exactly how it was when cellphones first became commonplace? I started high school in 2008 and had a flip phone at that time. Yea, literally everyone was texting behind their back, under a desk, or whatever but it was fine. If we got caught, the teacher picked it up and we could come pick it up at the end of the day.

I can imagine if the current “meta” is literally holding your phone in your hand for the entire school day that problems would indeed arise.

Personally, I think banning phones in the classroom similar to what I grew up with is the minimum. If students still have poor outcomes or are being bullied by other kids sneaking phones, then yea, collect them at the door or implement stricter punishment for students caught with a phone.

You can try it out. I would say it’s aiming to be a more modern Sublime Text, which is a win to be considered in the same category imo.

I can say as someone who moved from Texas to Western Europe almost 3 years ago, the health insurance situation is certainly an upgrade in many regards. The monthly premium is reasonable and the yearly out of pocket max is also reasonable if you have a good salary. I also have the option to pay the annual deductible as a part of my monthly premium so all care is “free” for the year. If you live on a fixed income or have a chronic condition, I can see how that would be a plus.

My only complaint would have to be the insistence that everything can be solved with a couple of aspirin and bed rest. While they’re probably right on the whole, nothing feels worse than finally mustering up the energy to make the appointment and travel to the office only to be told to go back home and do nothing. I came to the office specifically because I tried the home remedies and they didn’t seem to be working! I’ve also heard stories from others about twisting an ankle and being told the same thing. No xray or sonogram to double check, just “go home and relax”. I see quite a few people walking around with a limp which is probably just some form of bias on my part, but I can’t help but wonder how many people were let down by the system because a GP somewhere decided it wasn’t worth putting more resources into unless you follow their playbook first to a T. IMO it goes to show how systems can work for general populations but often fall apart when applied to individuals.

I think there can be a different way to think about CSS that can help with that feeling of never understanding it all. Recently I’ve heard people influential in the CSS world describe it as a “suggestion” to the browser. The browser has its own styles, the user might have some custom stylesheet on top of the browser’s version, extensions, etc etc and at some point CSS is really more a long list of “suggestions” about how the site should look.

If you embrace that idea to the fullest, you can create some interesting designs/patterns that can be more resilient. The “downside” is that this way of writing css will likely made the pixel perfect head of the marketing department hate you unless they also write code.

I think it’s also okay to say that some ways of writing css just aren’t relevant anymore. A good parallel in mind is building construction and general carpentry. These days, a quick 2x4 stud wall or insulated concrete forms is fast, cheap, and standardized around the world. However, many craftspeople still exist that will create beautiful joinery for what is ultimately a simple thing, but we can appreciate that art standalone. With CSS, I don’t suspect we will ever need to go back to floats or crazy background images or whatever but it’s nice that those tools are still there for not only the sake of back compat, but also as a way to tinker and “craft” something bespoke for a special project or just because you like it. Education will eventually catch up and grid and flexbox will keep gaining popularity until we decide that it’s too complicated and come up with some new algorithm. That can all be true though and you can bring value as a developer without knowing every single aspect to the public API.