skysight-inc/HackerNews huggingface dataset:
> The initial investigation found no evidence of threat actors accessing customer data or password vaults, meaning no action from end users was required.

I think the key word here is "initial" - they have no evidence thus far that user data was compromised, but that doesn't mean it wasn't, or even that evidence doesn't exist - right?

I get wanting to make a statement promptly and reassure customers but I'm not sure how valuable this is for users of LastPass. Should they just assume everything is fine until the company discovers it's not?
Your argument is very compelling. /s
While what you say is correct, the recent Ryzen 7000 announcement has shown that AMD remains much less greedy than NVIDIA, because with the top Ryzen 9 7950X at $700, the price per core has remained less than $50, about the same as it has been since the first Ryzen, even if the cores are now much faster.

Before the first Ryzen, only Intel Atom CPUs had a price around $50/core, while the better Intel Core CPUs had prices around $100/core. Then Intel had to also follow AMD and drop the prices for the top models to around $50/core (the "efficiency" cores in Alder Lake and Raptor Lake count as a half core).

So there is still hope that the RDNA 3 GPUs will have a more decent performance/price ratio, even if it is unlikely that they will be faster than the RTX 40 Series.
This is standard practice with big corporate RSA remote login.
To do so, you have to pay the full price of the phone upfront. Some people can't afford that.
Cannot wait to see if the market bears these prices without ETH mining!
Just let them become e-waste and buy something new. Turn on the stove and open all Windows when not at home while you're at it. SMH.

And that "not safe to use"? You think it's gonna explode? Worst case it doesn't work, but even that's probably pretty low risk. Hardware doesn't "wear" that way that quickly.
The 3090 Ti series was already pushing 450W so this isn't new.[1] And it's because they clock these things incredibly high, well beyond the efficiency curve where it makes sense. Because that's what gaming customers expect, basically. On the datacenter cards they quadruple or octuple the memory bus width, and they drop the clocks substantially and hit iso-perf with way, way better power. But those high-bandwidth memory interfaces are expensive and gaming workloads often can't saturate them, leaving the compute cores starved. So they instead ramp the hell out of the clocks and power delivery to make up for that and pump data into the cores as fast as possible on a narrow bus. That takes a lot of power and power usage isn't linear. It's just the nature of the market these things target. High compute needs, but low-ish memory/bus needs.

This isn't necessarily a bad or losing strategy, BTW, it just is what it is. Data paths are often very hot and don't scale linearly in many dimensions, just like power usage doesn't. Using smaller bus widths and improving bus clock in return is a very legitimate strategy to improve overall performance, it's just one of those tough tradeoffs.

Rule of thumb: take any flagship GPU and undervolt it by 30%, saving 30% power/heat dissipation, and you'll retain +90% of the performance in practice. My 3080 is nominally 320/350W but in practice I just cliff it to about 280W and it's perfectly OK in everything.

[1] Some people might even be positively surprised, since a lot of the "leaks" (bullshit rumors) were posting astronomically ridiculous numbers like 800W+ for the 4090 Ti, etc.
Apple phones have always been performance competitive with Android phones for quite a few years now, despite using cooling systems that maintain significantly lower wattage.

This means that Apple's processors are more efficient than the equivalent Android devices, but their cooling systems are very much critically designed.

Rather than decrease the CPU performance, they typically start dimming the screen first. This is extremely frustrating when outside and you need to see something in the sun, if the sun happens to warm up the screen. This is widely regarded as the biggest problem with Apple phones and thermal management. One user on YT who works on commercial HVAC on a roof in AZ, US mentions that Apple phones are unusable because the ambient temperature and sun will cause the phone to shut down and display a overtemp warning without doing anything, while Samsung keeps working.

The reason flagship Android devices do not have this problem is twofold: 1) Android device makers use a ton more cooling materials. Large area graphite film layered with a competition driven (among all Chinese manufacturers anyway) almost 70% coverage vapor chamber cooler. Only Samsung lags the industry here. 2) Different trade offs. Android phones typically allow surface temperatures up to 47C for high performance devices, where Apple probably believes users will complain of overheating if the device feels hot, thus targeting 44C. This is the back surface temp, not the chip temp. The stacked main board approach means that on a iPhone Xs Max I jailbroke to look at the temp sensor on, the most average of tasks like scrolling would spike the temp over 80c.

Furthermore, Android phones are capable of using the whole body to dissipate heat, but this will heat the battery and decrease its lifespan. Apple makes it clear in their design choices that they do not want this.

I played with the Pro Max in an Apple Store a day ago and it was not hard to negate the whole 2000nits thing in less than 30 seconds dawdling about the phone without even using the browser or apps that the phone doesn't come with. The brightness (triggered with another phone flashlight over the sensor) lasted for not a very long time.

Running WebGL Aquarium, which is the best approximation of a power wasting js/webgl application I could think of, the screen almost immediately dimmed another step. Running my finger over the surface of the phone with my finger to approximate a really terrible thermal image, it was clear that heat is not well spread to any region except the motherboard itself. By teardowns, there is a finger of graphite that avoids the battery and uses the top left of the screen. no heat felt there at all.

Whatever gains the 14 has by way of the aluminum plane under the display, (which was actually a rather effective heat spreader per thermal image from Max Tech and Geekerwan on YT) the Pro misses out on, probably because stainless would not have helped nearly as much, and that device is "too" thick and heavy as it is.

At least we know now that Apple are not entirely averse to heating up the battery a lil....
40 years later, officials reflect on “The Play” (Cal vs. Stanford)
https://blog.cloudflare.com/announcing-wasi-on-workers/ will probably open it up a bit for you with a concrete example
Your response seems to ignore the very article being discussed.

Or are you suggesting that if you're having trouble visiting sites because of Cloudflare, you should become an enterprise customer? (slightly sarcastic, but not completely)
Then go hack.

The point is, it's not an interesting hack for the vast majority of the audience. Because they've already seen this play out over and over and over.

It's like sticking your hand in a grinder and yelling "for science". The result might be new for you, and it's hacking by your definition, but I'm fairly certain the rest of the audience is OK not investing time into the experiment.
And many years of torture in solitary confinement.
The lapsus hack doesn't matter, no body is going to Read trade secret code.

What actually matters is the announcement of an open source kernel driver, similar to how AMD does it, which will allow for third party drivers like Mesa to exist, instead of manually reverse engineering everything.

https://developer.nvidia.com/blog/nvidia-releases-open-sourc...
I feel the same!

I work on regular ol' websites, that have some pages containing some moderate interactivity – so a few years ago the project adopted React to handle the frontend. I've found the experience mostly OK, but I sometimes get the urge to simplify things by leaning more on server-rendering / maybe using the URL to capture state...

and then realize I can't, and that this is Just The Way It Is Now. Because now all our devs expect to use React (or more accurately, its vast ecosystem of 3rd party functions of varying quality) to accomplish anything, and we forgot to screen for hires who can write their own JS+HTML or who understand how the response/request process works in a web application. (oops!)

"React hires are easy to hire for" so that often drives decisions, but I am skeptical my project ever needed React (or any hyper-optimized-for-SPAs-feature).
Everything related to Trump is ALWAYS about self promotion - either his own or using him as a means to promote themselves. It is the central motivation to EVERYTHING he does as well as everyone in in his orbit.
This is a very insightful comment and there's a lot of good points in your Twitter thread, so thank you.
Does VRChat count as a game? In a very populated instance with 50+ people it can take up to about 20gb of vram.

Honestly everything VR takes up huge amounts of vram, it's not possible to run No Man's Sky at max settings with only 8gb vram, and you still might need to dial down some settings with 12gb vram.

This is with a Quest 2, I'm guessing headsets with higher resolution will be even more demanding.
Cameras are bad enough. Audio recording is even more intrusive than cameras.
We've definitely seen 'memory go bad'. But, our failure rate is in the single digits, across a huge sample set across multiple years and in relatively extreme conditions (4 seasons, outdoors).

If you're buying something for like half of retail and rolling the dice on it, I think it is a fair bet. Even if you only get 1-2 more years out of a card that has been used before (for any purpose), then you've done well.
I keep saying we need a state-ful GUI markup language standard so we don't have to re-re-re-reinvent real GUI's with JS+CSS+DOM. Those weren't meant for real GUI's and retrofitting creates bloated, buggy, ever-changing messes. GUI's have been around more than 30 years, why can't we network-ify its common and loved idioms?
In 5 years if no one else is using Hotwire

I think that's the opposite of what he is saying. Because React is updated and changes frequently, your code becomes obsolete unless you update to follow the latest changes. In theory, if everyone abandoned Hotwire, your code would never be obsolete or need changes, because Hotwire would never change. In reality, as browsers and web standards change, frameworks need updating.
In the short- term, definitely. An argument that I’ve heard before is that in the long-term, companies like LastPass will gain improved security through fixing the holes that are breached.

“What doesnt kill you makes you stronger”, so to speak.

I’m thinking that something like unrestricted dev access for four days would be more like a death blow, though. I suppose that depends on how much source code was exfiltrated and how many backdoors got planted in systems, etc.
Then there is no way to measure wealth at all, its just all a mystery.
Tom at MLID pretty much confirmed as much in his recent two broken silicon podcasts. Nvidia is pricing this way so they can run the 4k and 3k lines concurrently.
Iirc the Lightyear Zero can do over 6, plus it charges while driving.
However you choose to exercise, measure resting heart rate and maximum heart rate to fact-check.

https://www.ntnu.edu/cerg/personal-activity-intelligence#Bet...
React is low level. Svelte and Solid are low level too.

You are dealing with particular values and wiring everything meticulously.

Whenever I write stuff using https://rxjs.dev, writing React feels the same.

Using ExtJS years ago felt higher level than React.
Luckily seems you have forgotten about the Internet Exporer
Very cool! Congrats!
Rule also implies universality, which is how I interpreted it here. I was saying this is a new, ‘limited’ belief.
Try MSFS in VR on ultra settings. With mostly high and ultra I'm sometimes able to get 30fps on my quest 2. Nevermind something like the Pimax 8k or upcoming 12k.

That sim eats graphics cards for breakfast.
Yep. There are "simple" things we can do that will make things better but that can't happen until we agree to do it.

And for that to happen we need to understand it.

And for that to happen we need to talk about it.
I use similar flow with notion
I found OpenCL useful for a narrowly focused project at work. I used the Python OpenCL bindings. My experience is somewhat dated as I did most of this about 4-5 years ago and then stopped paying much attention to it. That code continues to run in production without any real maintenance, which I consider a point in favor of it. I.e. it just gets redeployed to newer OS and Python installs and continues to work.

From others' comments here, it seems there hasn't been much development since then in OpenCL land. I imagine details of device support might vary over generations of hardware and driver releases... I made use of half-precision float storage but ran compute at single-precision since my devices did not offer fast half-precision math.

This was small "hpc", i.e. a task that would run on one workstation or modest single socket or dual socket x86_64 server or VM. The most performance-sensitive aspect was that it was also used during the data loading/startup phase of an interactive tool. So a human user was impatiently waiting for results. The first prototype was just using Python numpy routines for convolutions, etc. I used OpenCL to get running time from many minutes down to tens of seconds and called it good enough.

I enjoyed that I could run the same code on a workstation GPU with the NVIDIA driver or via x86 multithreaded SIMD using the Intel driver. I did not do any real work with Intel nor AMD GPUs because of the hardware selection we had on hand. I also needed more than 6GB GPU RAM for it to be worth using. Even my Titan X with 12GB was only about 2-3x faster than using x86 SIMD for my problem, due to the complex tradeoffs between RAM and bus bandwidths for data transfers. This is after I'd already done some algorithmic optimizations to bring down the compute/IO ratio.

A big thing I hear others talk about is the rich development tools with CUDA and the relatively impoverished OpenCL tooling. I am old school enough to get along without it. I was able to compensate for limited Python OpenCL tools by doing some of my development and debugging cycle embedded in hacked up variants of my own viz tools. You might think of this a bit like debugging with printf, except my print statement could send a dense 3D array into an OpenGL-based renderer on my workstation.
Blaming human nature on capitalism?

Is this something that magically doesn't happen in top down managed economies?

Care to point us to an non-capitalistic economy where this type of irrational behaviour doesn't happen?
It's actually very accurate.

web1 - it's open!
web2 - it's open (but really controlled by social media billionaires)
web3 - you own digital property but good news, you can be a landlord and get money by leasing out that digital property, or you can be a speculator, or you can be a serf and work in an nft farm. Ignore the wash trading, paid celebrity endorsements, and the rugpulls.
Infrastructure and other energy use would be counted as part of the product in the form of embodied energy[1] of the end product. This isn't about distributing blame. It's about getting average energy use per person to <2000W on a societal level.

[1]: https://en.wikipedia.org/wiki/Embodied_energy
Where are good examples of clean, well-implemented React code by your definition? Because your comment perfectly encapsulates my experiences and frustrations in learning and using React off-and-on over the past 8 years or so.

React is the one tech that really freaks me out because every time I have to dive into it, it's a completely different beast and it feels like so many people actually writing in React are just effing CRAZY

Years ago I wrote a 12-line-or-so JS "framework" that did one-way databinding, it accepted a fragment of HTML with template strings and replaced those with the data you wanted... it could handle thousands of updates without falling over (though updating the whole table would freeze the browser for a half second) and last I checked was still in production doing fine. But now nobody understands it and I'm fielding weird questions about why X framework wasn't being used in 2015 when I wrote it. And it feels like 90% of what I do in React is the same thing! (Simplifying, sure, but my point is that React feels bloated as hell and reinvents the wheel way too much)
It's possible prove a negative.
One startup, our MVP launch date (very hard date; miss it, and the company is over) was moved to earlier, by customer's manufacturing schedule change, just as half our small, high-powered engineering team got sick.

So I took the existing plan, from before the latest reality happened, and:

* Turned plan into refreshed sorted spreadsheet rows of prioritized tasks and estimated durations and assignments.

* Culled tasks very heavily and sometimes painfully.

* Kept in mind that the system had to work immediately at launch, and had to keep working, with production line uptime and correctness. (For example, there were some non-obvious system robustness/resilience tasks that I added, even as I was removing most other tasks.)

* Looked for opportunities to do things smarter, from the remaining essential tasks.

* Made sure the sick people weren't assigned to anything that absolutely had to happen.

* Kept updating the plan, sometimes multiple times a day, as tasks were completed, problems found, etc.

* Made sure that the estimates always said we'd hit deadline.

All this planning was rapid and intense, not "let's take a day to plan, and schedule some meetings, and have regular check-ins, etc.", and captured in a single view (the spreadsheet).

It was successful, ended up with 100% software uptime and correctness, for the entire contract period, of over a year. Some of that was because the technical cofounder who'd done all the initial work had experience with critical systems, and I followed through in the same spirit. Some of it was luck. Some of is was being vicious and smart about what work was done. Some of it was misery, knowing that the company, and a lot of people's livelihoods and career goals, relied on this coming together in time and working.

As for how to shield people from ulcers in a crunch: if anyone has to get ulcers, it should be leadership, quietly, from figuring out how to make this come together successfully, without the entire team exploding with ulcers.

And the team should see that leadership is all-in on making this be a success, and every individual implicitly buys in on staying committed to the team and project, and the team rises to the smart things that they are asked to do.

(Note: In this case, I used a spreadsheet, but in other cases, the single source of truth view for the entire project would more likely be a good Gantt diagram, or maybe a Kanban board. What's important are that it always reflects the best information and current decisions&activity, everyone is working from it and understands their parts in context rather than as checkoff tasks out of context, and it shows the project coming together.)
Depends on what you mean by global state. You don't have access to a single pool of global variables. You only have access to what you put there and what you've been given.
I would love to buy 90% of the people that throw the word fascism around a dictionary because like you they have no idea what it means.
> Having children is not easy but not super hard either if as a parent you have things in order.

I wish it to be super hard and not cool tbh. If you want to get that kind of coolness then go 996 and stop complaining, please. Somebody might be disgusted about overpopulation of the Earth, btw.
Actively coding in Java in a large system at the moment (so we can't Kotlin), but if I were to start a greenfields I'd give serious consideration to doing it in Kotlin.
It’s absolutely required for most multiplayer games. Many need random ports and some even refuse to work if UPnP is blocked even if you manually open a port for them.
There is a section in the linked announcement titled "Why use a WebAssembly Runtime?" that hopefully answers your question.
I think an investigation is needed because I feel like Nvidia and AMD are price fixing, and we're not having a whole lot of luck with competitors in the space.
Leave. Unless you really love the company. Then talk to you manager/anyone who has an impact on future projects about this, ask what the plan is to prevent this, and then leave.

Deadlines are typically not strict unless there is a contract in place. They can be moved. Asking people to put in some extra time once in a while is fine, even if not ideal, but not for extended periods of time. That leads to burnout and the company is valuing delivery over your health and your future ability to work for them.
Recently bought a RX 6600 for (€/$ 285), very happy besides not being able to (easily at least) try out stable fusion ;)
It’s pretty easy to do a full export from LastPass and import it right into KeePass.

Things like notes and financial information might need special attention, but the basic process is prety quick.
In my view, hooks are more about managing state dependencies, rather than functional programming, per se. So they're more useful for simplifying methods like componentDidUpdate, rather than componentDidMount. When you need to detect changes by comparing prevProps to this.props or prevState to this.state, the logic can quickly get really ugly. Instead you can just put the relevant prop or state you want to monitor in the dependency list of a hook, and it will be triggered whenever that dependency list changes.
That's a great description. If you have a solid understanding of high school math and are willing to put in the effort, this is a book that will reward you.
Oh, absolutely. Pretty much every distinctive feature of prototypal OO is best classed as "please, never ever actually use this". Adding the "class" sugar and general agreement to pretend the prototypal stuff isn't there, though, made JS OO usable-enough. But yeah, it's not great.
There is a meme in the US media that only if we are more like social democracies of Europe, it would be a paradise here. Reality begs to differ. UK has NHS and free college and still went for Brexit and Boris. France has everything Bernie Sanders wants and yet Marine Le Pen has been the runner up choice for the President in the last 2 elections. Italy is about to vote in Meloni. And now the socialist's dream otherwise known as Scandinavia is seeing the rise of far right. Let's not even talk about Hungary or Poland.

If European governance model is so awesome based on HN comments and Bernie followers, why so much support for the far right?
Unless someone breaks thermodynamics, there is really no way to reduce to 2000W without reducing consumption of goods by a factor of 10 in the west. That means a new phone every 20 years instead of 2 (global mobile device supply chain is huge), getting new shoes every 10 years instead of 1, getting a new car every 50 years instead of 5, etc.
Thanks for sharing! Please share any ideas of feedback
I think it is funny that originally Java only had green threads, but then they were replaced with native threads, and now java is getting green threads again. Obviously a lot of development has happened in that area since, but still funny.
I would actually be quite interested in seeing some numbers to back that up, but I'm not sure if there have been studies on the damage of mining yet.

In some ways, letting a GPU run at a constant load (and thus constant temperature) is less damaging than a typical gaming workload I imagine, where the temperature fluctuates often. In other ways it probably isn't (e.g. atoms of the chip 'migrating' over time with the constant electron flow, though I have no idea how much of an issue that is with modern chips).