yxhuvud

Sorting lego? What. Just build stuff, why would you sort it.

The posts entire point is that it is too early to tell.

Strangler pattern can make sense for that, and that may involve that kind of adapters. But it also involves actually finishing the job and make certain new semantics go through the whole thing and restructuring until it makes sense.

Not uncommon, it is enabled by default in Go.

Sounds like they store the integer in the reference itself in that case. Which also is how Ruby does things (though Ruby has to decide what is what at runtime and thus steal a couple of bits off every integer).

The parallel assignment just work mostly like it does in ruby so that doesn't look weird to me (except the need for 'var' in the first place).

Agreed on the rest, though I don't understand what the problem would be with recursion. Is it using reference passing also for primitives like integers?

Stronger how?

Definitely more explicit by default though.

But yes, very neat. I'd miss Enumerable though, if they manage to get that to play with manual allocation that would be even neater.

It is also slower than any other interpreted dynamic language in wide use.

> Maybe base python is more optimized than base Ruby

Not since before Ruby 1.9, no.

Getting a JIT from underwhelming to actually good is always going to be a whole lot of iterative work to remove blocking parts of the existing implementation. In Ruby-land we have had a good JIT for a while now, but it took many release cycles and a ton of resources before it was able to outperform the non JITed version when using Rails. Don't expect quick fixes that make great strides and any investments in it needs to be persistent and apply over time.

It boggles my mind that it apparently is the case that such a popular language as Python isn't able to get the resources to do this.

I agree that the SaaS solution will be a winner, but the price diff cannot be too big or it would be too economical to run it yourself.

Paywall.

Yes, especially as not all trees are the same age, and the older trees were grown defined by even older trees that are now gone.

The generated trees look absolutely amazing. Adjusting the process for different lighting situations seems straightforward too - freestanding trees look different from those in woods.

How is it news that they have preferred tools that they enforce the usage of? Any decently competent IT org should do the same.

Because it is a nice language to write elegant and performant code in. If that is not enough motivation I guess it is not a language for you.

While you are right in that it is impossible to verify they work as advertised, it is not impossible to detect certain categories of failures. Like only generating values 0-255.

No, but it would sometimes be nice if they sometimes raised questions about what is important and what isn't

In my country we have people, lots of them, that would prefer to forget that renewables forget and to massively build out nuclear to meet demand. In that situation it makes sense to bang the energy cost drum. Yes, obviously the network needs to be kept running and that may take some added nuclear and investment in the existing hydro plants, but at the end of the day a sizeable part will going to be renewables as it is so much cheaper.

I still would not appreciate having airborne panic attacks on a plane.

Part of that is much of the point behind snaps (and just as true of flatpack for that matter) - once applications are put into sandboxes many things break. And while it is often easy to erect walls against unwanted use it takes a lot of thought building abstractions that let people do what they need in a controlled way that don't leave the system as open when compromised.

But yes I agree, it is definitely a big change compared to how things traditionally have worked. The question is if it is a necessary direction.

There is a flag to install a snap in classic mode, which I think would allow it more access, but I've not seen more fine-grained control than that. Perhaps it exists, I have not had a reason to look.

As for X11, I'm on Wayland and wouldn't expect xeyes to work. What X11 programs still is used seems to work fine in Xwayland, but I don't use VNC so I don't know how they interact.

So I don't know if these are solved, sorry. I suppose I have simpler needs.

Questions like this are easier to answer if you specify which problems you refer to. They have fixed a ton of issues since it was added to 22.04. If the issues you complain of is fixed or not, that is impossible to answer without more information.

I reacted the same. What could be a bad sign though is if they try to sell it and they dont get what they want.

Maybe, but 50% growth in a stock over 25 years is fairly bad.

For Cisco it took 25 years.

But that is assuming they survive the bust, which is not a given.

Some people just like running around with scissors..

Stupid headline, we are still on the path towards it.

> 100% knowledge of the code in their projects

That stops working once the code reach a certain size/complexity limit. It is a different limit for different people, but there is a point where there is just too many parts to be possible to fit in a head. There is also a middle stage where everything fits, but can't be accessed all at once but require some time to retrieve specifics when looking at areas not in recent memory. The middle step is more achievable the easier the code is to reason about by black boxing parts.

Part of the problem here is that large parts of the cloud seems to be stuck in 2017 when it comes to IO speeds and latency.