Follow Slashdot blog updates by subscribing to our blog RSS feed

 



Forgot your password?
typodupeerror
×

Comment Re:SpaceX's "Starship" uses methane (Score 2) 102

While getting to orbit on LNG is a big achievement.. if the rocket isn't reusable then I think the author is being extremely biased by declaring a "winner" on that one point. I'd say at most this is a solid step on the way to reusable LNG rockets.

SpaceX, ULA, and Blue-Origin are all testing big reusable LNG rockets. The LNG-fueled Vulkan is supposed to liftoff later this year with 5x the capacity and a reusable design. If that actually makes it to orbit it will be something to crow about. https://en.wikipedia.org/wiki/...

Comment Re:Texas Fixed Rate Plans (Score 1) 203

Low-income Texans are getting hit. In 2016 Texas abruptly stopped their government assistance program called “Lite-Up Texas” and replaced it with a patchwork of deals electric companies could offer to low-income residents. https://www.electricchoice.com...

LIHEAP does still offer “Crisis Assistance” to low-income Texans who are having their electricity turned off; although you have to apply through a patchwork of local government entities so it’s likely this is difficult for most people to use and is capped at $1600. https://liheapch.acf.hhs.gov/n...

Comment Re:Making AMD clones has to hurt (Score 1) 79

Every modern JIT heavily relies on 'ahead of time' optimizations for speed(Including Rosetta1). Rosetta 2 takes any AMD64 binary and runs it immediately(including AMD64 programs that are other JITs which emit AMD64 code which is then executed). I would be very surprised if you can find a commonly used JIT that doesn't do ahead of time optimizations. Also, very very few programs are dynamically generated so in the real world the performance the performance of the truly dynamic part of a JIT doesn't matter.

Ahead of time optimizations that exist in Windows-Arm would likely have made Itanium's JIT IA-32 Execution Layer super fast for 99.9% of Windows apps. https://en.wikipedia.org/wiki/...

Comment Re:Making AMD clones has to hurt (Score 1) 79

Itanium wasn't a great design in many ways, but it did have really neat little bits like VLIW which was supposed to make JIT work. Intel never delivered on JIT for Itanium but Transmeta had a really performant way of running IA-32 code on their 128bit VLIW processor during the same time.

We seem to be on the threshold of JITed regular programs being the norm. MacOS runs AMD64 code on their M1/M2 Arm CPUs faster than Intel/AMD CPUs(check out Apple's "Rosetta 2" that lets x86-64 apps run on M1/M2). Windows arm64 runs IA-32 and AMD64 apps pretty flawlessly through Microsoft's emulation layer.

Transmeta's patents all went to a troll when they went belly up, but those patents are now expired.

If Intel did a IA-128 that was a beefier Itanium design with a handful of flaws addressed I could see it doing well today. Microsoft is in a better position to do JIT(because it already works on Arm). A beefy VLIW is perfect for AI/ML. Intel's AI/ML chips are still VLIW and do very well. https://www.tomshardware.com/n...

Comment Making AMD clones has to hurt (Score 2) 79

Intel gave up on their 64bit ISA ~2012 and I imagine that gutted a lot of their engineering. Whether the engineers actually left or were just super jaded doesn't matter... licensing AMD's x86-64 ISA for all their future chips had to hurt.

For those that don't know; Intel's earlier ISAs (IA-8, IA-16, IA-32) were the standard for Windows PCs. Intel's IA-64 was called "Itanium" and was really neat from an engineering perspective. IA-64's biggest flaw was that it ran Windows IA-32 code poorly compared to AMD64. Intel licensed AMD64 and developed both IA-64 and AMD64 chips for awhile before throwing in the towel on IA-64.

In the 2000s AMD K8 CPUs were cheaper and faster than Intel. The main thing Intel had over AMD during the K8 era was MASSIVE factory capacity. Intel could deliver chips in quantities that AMD couldn't. AMD embraced fabless manufacturing early and the rise of several really good fab companies set AMD up for success.

Comment Re:Who is at fault - Google or Apple? (Score 1) 4

Chrome isn’t the default browser on iOS. Safari is the default

Chrome on iOS is just a wrapper around Safari. Apple’s JavaScript renderer is the only thing on iOS that is allowed to do native JIT, so Chrome effectively has to use it and uses Apple’s HTML/SVG/etc renderer as well. Chrome started as a fork of Apple’s Safari browser, so they share a lot of features/bugs so you mostly don’t have to care.

Submission + - Twitter cuts off third-party apps (macrumors.com)

gabebear writes: Twitter this week confirmed that it is no longer permitting third-party developers to create Twitter clients, with the information quietly shared in an updated developer agreement that was spotted by Engadget.

Comment Outsourcing (Score 1) 52

This is expected when you outsource. Taking lucrative contracts out of Russia is exactly what the sanctions were meant to do and MSI and Alexey should have seen this coming.

This Alexey sounds like a contractor who was allowed to much leeway and thinks he has MSI by the balls. I have no sympathy for anyone involved.

Comment Re:That is a sign of maturity (Score 1) 108

To be fair, MacOS and Windows both fail to support monitors running different refresh rates in fairly normal workflows. Using monitors that can't be synced is simply a really weird use-case that probably shouldn't be optimized for.

I tried Wayland on my work desktop for a couple months and it was fine(I like KDE Plasma). Wayland wasn't better, but I didn't NEED to remove it after trying it so I left it. My company locked down parts of our windows manager setup which made it difficult to use Linux locally. Now I mostly remote into my work desktop from a MacBook so Wayland is now totally worthless to me.

Slashdot Top Deals

Those who can, do; those who can't, write. Those who can't write work for the Bell Labs Record.

Working...