flukus

If something like this is financially viable (doubt) then it sounds like the density already exists and the problem is the restaurants aren't near the people. All the replies are focused on the density you mentioned but mixed use is probably the bigger and far more easily solved problem.

Letting restaurants open nearby to where there are clearly a lot of people is a tried and proven solution, not gadgetbhan for food.

Probably quite circular too, the labor costs are high because the housing/COL was allowed to become so high.

Flight booking systems still seem to be stuck with it, even newer fields like email are always in all caps.

Mine was around then too, mostly because the geocities page builder applet was such a dog.

A more charitable interpretation might be that getting under the cut off is why it's one of the first treatments available. More treatments will become available as the overall costs start beating out the costs of living with $disease.

> yet we tend to only hear about how humans need to cut back

There's also financial reasons to do so, with livestock the financial reasons are likely reversed.

Beside that, anti-biotics also have side effects that can make you more sick, their use is not just unnecessary but counter productive. Some of the side effects can be serious and long term, like changing your gut bacteria.

> It's got to be way easier to hire Angular developers than it is to hire someone who wants to eek out the maximum performance with this lightest-weight approach.

I disagree, at least around here. Frontend developers with react/angular experience are a hot commodity and really hard to hire, yet just about anyone from any tech tech can knock out html and some minimal css.

It seems endemic, especially everywhere that's not a product company. I think it was mythical man month (maybe earlier) that pointed out the 90% of the cost of software is in maintenance, yet 50 years on this cost isn't accounted for in project planning.

Consultancies are by far the worst, a project is done and everyone moves on, yet the clients still expect quick fixes and the occasional added feature but there's no one familiar with the code base.

Developers don't help either, a lot move from green field to green field like locusts and never learn the lessons of maintaining something, so they make the same mistakes over and over again.

If nothing loads nothing gets cached and you can get in a cycle of very slow 404s.

The current abomination I'm working on avoids this by caching the errors and serving them for several hours...

Hiring a car for specific trips is probably much better, depending on the % of those use cases. That goes for other factors like towing capacity too.

Cars are already very expensive for something with such a low utilisation rate.

Depends on what "taking off" means for the start up too. Taking off at a mass consumer scale might need that flexibility, taking off and even getting to market saturation in a specific B2B might be achievable on a raspberry pi level hardware. There are many more of the later.

Almost 20 years ago we had to write our own database with indexing for a software dev class. It was crap by every definition possible

But that learning experience and having a rough idea of what sql is doing under the hood is still useful to me every day.

> If you want to fire people for performance or other reasons, it's true that a great time to do it is during layoffs

That really depends on the jurisdiction, in Australia and mich of Europe you can't replace someone laid off for a certain amount of time.

I've been through all the ups and downs around Ubuntu and gnome, but at least those changes generally happen at a time of my choosing too. I don't go to a commonly used app one day to do something quick only to find the entire UI was updated overnight.

Of course even the cli world has had it's changes though, systemd alone made decades of documentation obsolete.

Nowadays we shouldn't be allowing cats to be outside unsupervised in any case, they can be devastating to local wildlife, including these clever cockatoos.

I deal with so many over complicated enterprise solutions that would be much better with this level of abstraction.

CGI scripts are basically FaaS on your own machines.

Nothing goes through decades of testing, they go through human trials and then monitor safety at a mass scale for a year or two and then they're done. Same as with the covid vaccines.

> Fraudulent charges can be reversed immediately

This isn't really a benefit, it's a fix to a problem caused by credit cards that doesn't happen at all (or at least rarely) with debit cards.

> Which never happens,

It has happened to me, an update broke my sound card and I didn't know until I tried to use it at a time that was extremely inconvenient to me.

> Submit a bug for a DE, and they might tell you to install the newest version to replicate it there (yet you're on Ubuntu...)

Known bugs have known work arounds, I can deal with that. What I can't deal with is surprise new bugs in cutting edge software.

I like the polish of manjaro, I just prefer the stability of debian. Polish doesn't mean much when a rolling release breaks your computer.

People have also switched to larger and more expensive vehicles in addition to these mandatory costs, so I'd say the mandatory costs are mostly a non-issue, otherwise we'd be seeing people cut costs elsewhere.

https://www.greencarcongress.com/2020/01/20200101-jato.html

Won't this be flat out wrong when something you're joining to has a condition in the where clause? Something like this:

  select * from Car
  inner join Color on Car.ColorId = Color.Id
  where Color.Name = 'Red'

You can't get the correct paginated list of car id's without doing the join in the first query. Even more wrong if you're ordering off the joined table.

Better yet, put it in a .rec file for the best of both worlds: https://www.gnu.org/software/recutils/

It's a consequence of having our software run on other peoples computers. 20 years ago it wasn't really an option because most software was installed and pushing updates was hard, but now everything can be updated without the user even knowing. IME there's a lot of people on HN that will even defend this sort of A/B testing.

This is why I like debian, I never open an app to find out the entire UI is changed while I was asleep.

I like an SPA pile on as much as the next person, but I've seen similar ignorance from asp.net webform developers many years ago. Some of those were even "experienced" developers.

I think there was some network access going on in the start menu for windows 10. I once had my mobile internet drop out while opening it and it was unresponsive until it timed out a minute later.

I have a recent Nokia that has all of the above. Except for maybe the "high quality" part, I'm not sure if the phone or aging headphones are to blame there. But the battery is a monster, though not replaceable. There seem to be plenty of others on the market.

I have joined the bluetooth headset world though, shokz openrun finally had a compelling feature set that I couldn't find with wired headphones.

> Out of four hours you get about 10 minutes of meaningful detail about the incident

Most documentaries have always been very low on information density. Even universally loved ones like something from David Attenborough are mostly a collection of disconnected (yet amazing) film snippets with a bit of commentary over the top. It's only gotten worse as narrative has become more of the focus.

There are exceptions, but when it comes to conveying meaningful information and detailed analysis youtube is far superior than mainstream documentaries.

The probably is we've coupled the gui and the service, the people making the UI have a monopoly and no reason to improve. Same goes for spotify, audible and just about every streaming provider these days.

> how does a team of actually skilled engineers who wants to get a start in this business compete with these sales companies?

You don't. There's an inverse effect where you don't really want the clients that go for these big consulting companies because there's just as much crap on their end and they'll drown your skilled team in bureaucratic nonsense. You want the smaller clients where your technical skills complement their domain knowledge. There's still a lot of marketing and management, but the people that actually do things can talk to each other.