OpEx means that if demand for your service goes down, cost goes down, your hardware does not become a capital liability since it depreciate fast. Way easier to justify changes to it too, you don't need a purchase project to get new instances, you're already "approved" and the contract was already signed with fluctuating costs. Needs more hardware? press a button, no need to research vendors, get contract negotiations in place.

AWS makes the life of finance and leadership a lot easier because they spend a lot of money justifying their superiority in ways that you don't have to think too hard to use and be taken seriously. They're to CTOs what think tanks and lobbyist are for lawmakers.

"No one got fired for buying ibm" for the new era.

There is a lot of truth in AWS propaganda, they're great for many things. But some of it is built on lies, cost being one, performance another.

Opex looks nicer on the sheets than capex for large deployments. Incredible high investment from AWS on luring in C level with "white-papers" and promises of cost and governance magical revolutions. I've heard the promise of cheaper, faster where you can focus on "innovation". I am yet to see any of it become a reality.

Modern IDEs will show you the type of anything at all times. I do not understand your point unless you're doing raw text editing of Java source.

Those keystrokes are not just saved on writing, they make the whole code more legible and easier to mentally parse. When reading I don't care if the variable is a specific type, you're mostly looking whats being done to it, knowing the type becomes important later and, again, the IDE solves that for you.

> Modern IDEs will show you the type of anything at all times. I do not understand your point unless you're doing raw text editing of Java source.

The word "String" "Integer" et al. + "var" is too much real estate for being explicit. Sometimes, I'm looking at the decompiled source from some library that doesn't have a source package available.

> Those keystrokes are not just saved on writing, they make the whole code more legible and easier to mentally parse.

This is incorrect. Repeating it doesn't make it true. For trivial code (<10 lines) probably seems fine at the time. Lots of bad practices start with laziness.

Changing practice because an author thinks a function is small enough when it was written, is a recipe for unclean code with no clear guidelines on what to use or expect. Maybe they rather put the onus on a future reader; this is also bad practice.

To me var is what makes modern java somewhat readable and more bearable. It was always a joke that it takes too long to write anything in java because of the excessive syntax repetitions and formalities. To me that joke is heavily based on a reality that modern Java is tackling with this quality of life features.

I get the attraction to var, but I, personally, don't use it, as I feel it makes the code harder to read.

Simply, I like (mind, I'm 25 year Java guy so this is all routine to me) to know the types of the variables, the types of what things are returning.

  var x = func();

doesn't tell me anything.

And, yes, I appreciate all comments about verbosity and code clutter and FactoryProxyBuilderImpl, etc. But, for me, not having it there makes the code harder for me to follow. Makes an IDE more of a necessity.

Java code is already hard enough to follow when everything is a maze of empty interfaces, but "no code", that can only be tracked through in a debugger when everything is wired up.

Maybe if I used it more, I'd like it better, but so far, when coming back to code I've written, I like things being more explicit than not.

1. Just because you can use var in a place, doesn't mean you should. Use it where the type would be obvious when reading code like

  var myPotato = new PotatoBuilder.build();

not like

  var myFood = buyFood();

where buyFood has Potato as return type.

2. Even if you don't follow 1, IDEs can show you the type like

  var Potato (in different font/color) myFood = buyFood();

Yes, well expressed. For that case using var is not a wise approach.

It does help when writing:

    var x = new MyClass();

Because then you avoid repetition. Anyways, I don't ever use "var" to keep the code compatible with Java-8 style programming and easier on the eyes for the same reasons you mention.

I have the opposite feeling. var makes it easier to write but harder to read/review. Without var you know the exact type of a variable without going through some functions for example

While I was there I did some search around and it seems that the wind, weather and soil is just part of it. The largest reason is sheep. They'll eat any tree before it has any chance of growing. So you get naturally sparse growth already, add the sheep, you get grass everywhere. Which makes everywhere very walkable and surreal at the same time. Plenty of trees on cities and gardens.

> It's traffic that is completely below ground which means that no streets above are burdened with it, it's all electric so no emissions

So are modern subways. Cost is a major point tho, subways are designed to move waaaaay more than 30k people a day for much less, but costs of building are much higher.

This is only 1.7 miles and a novelty, I would not know If the differences hold for Tesla on other places or when scaling up. My suspicious is that it does not.

I also wonder that if you use the same tunnel they did but modify the cars to run by themselves using traditional techniques, would the operation get cheaper but the shortcomings be more glaring.

This is nothing compared to Tokyo Metro, or even the New York subway. Stop comparing failures to other failures like they are successes.

You are comparing the Vegas loop to a tunnel in Tokyo the biggest metro on earth.

That's like saying a car is slow because it's not a spaceship.

Can you cite that Tokyo is the biggest metro?

When I say metro I'm talking about metropolitan area not the subway.

Tokyo has 37 million people so it's comical to compare it las vegas which has less than 700k.

https://en.m.wikipedia.org/wiki/List_of_largest_cities

Hey. That's my network name.

Funnily enough weed is more legal in the US than Norway.

Not federally it isn't.

They stopped giving a F and started to give a S (lots of it)

I think any of the "off the shelf" gotek emulators should suffice for this. They're made for people to keep playing games on old hardware. I would assume copy protection and other shenanigans would be the creme de la creme of abusing the hardware.

This is to get rid of the media only. You'll still be using the original compute hardware. But it would be an interesting step.

I feel that most of the desire to upgrade is cultural and not technical. People love to talk about the floppies being used while its just a small part of the equation. Cost and risk of creating a new system with the same reliability expectations is hard when the incumbent has decades of iteration. For systems that do not require more performance or energy efficiency the accounting on upgrading looks very different.