skysight-inc/HackerNews huggingface dataset:
> Jennifer Kelly, a freelance copywriter in the picturesque New England town of Walpole, N.H., feels bad for any young people who might try to follow in her footsteps.

How many typists did word processors put out of jobs? Before, if you wrote a paper or document, you would write it out by hand in a notebook, correct what you wanted and then a lot of times pay a professional typist to quickly and correctly type it up for you. This was a lot better than trying to do it yourself, and spending many frustrating hours making mistakes and using whiteout and retyping.

You will always be able to find someone adversely affected by technology. For example, refrigeration put icemen out of work.
If the earth was a uniform sphere without oceans and mountains, sure.
They likely can have some fusion reactions (if they use fusible fuel, like D-D). Fusion is not that hard to achieve, you can do that on a table-top scale (Farnsworth Fusion).
> The kite in question has been named Seawing, and may help ships reduce their fuel emissions by between 10 and 40 percent

Not KM but 822m seems pretty close. I think you’re grossly overestimating the benefit from the kite. Seating’s current website says:

> A 1000m² sail surface to harness the power of the wind and tow ships. Based on modelling and preliminary land-based tests, Airseas estimates that the Seawing system can reduce fuel consumption and greenhouse gas emissions by an average of 20%.

I don’t think better routing will increase that to 80% even if you combine it with next gen tech that knows wave patterns and when a slot will be available to minimize speed and energy loss.

We need a path to remove fossil fuels from ships (& planes). There’s also industrial applications that need high heat that solar can’t really accomplish. Finally, solar & wind need insane battery capacity which when included pushes the economics strongly back in favor of fission and fusion.
Maybe it is, but HN has a broader audience and the title loses context when used here.

(Also, I think Fastco should realize that they're being read by English readers all over the world who only know Celsius, but I guess they do measure their audience.)
With how energy-dense uranium is, we could pay all the workers to wear full-body radiation suits and it wouldn't make a dent in the price per MW.
The cameras are only used at night, since that's when meteors are visible.
It's called V-Cache.
192 cores per socket? If so, that's pretty wild.
I wasn't aware of either of those, so thank you very much for those referrals I shall take a close look at :)

(Are you by chance the author of org-latex-preview, or is it a coincidence of usernames?)
Looks like this is a WordPress site, and the HTML source does contain:

<link rel="alternate" type="application/rss+xml" title=" &raquo; Feed" href="https://anandsanwal.me/feed/" />

So I'd assume that https://anandsanwal.me/feed/ is indeed the RSS feed. IIRC, /feed/ is what WordPress uses for that purpose.
What actually happens is you hit the concurrency limit and return 99k throttling errors, or your lambdas will try to fire up 100k database connections and will again probably just give you 99k-100k errors. Meanwhile a 1 CPU core container would be done with your burst in a few seconds. What in the world needs to handle random bursts from 0 to 100k requests all at once though? I struggle to imagine anything.

Lambda might be a decent fit for bursty CPU-intensive work that doesn't need to do IO and can take advantage of multiple cores for a single request, which is not many web applications.
I remember that, too. There were also just a lot of places where it’s like … your data is already in a SQL database, why not get better at reporting queries until you’re running so many of them that you don’t have an easy path to handle them? It was especially tragicomic in places where they were basically hoping not to need to hire analysts with technical skills, which is possibly the most MBA way ever to very expensively “save” money.
CHERI-RISC-V is being standardised [1], Codasip is working on a commercial implementation of CHERI-RISC-V [2], and lowRISC is working on the Sonata project [3] implementing CHERIoT.

The Early performance results from the prototype Morello microarchitecture report [4] predicts the overhead between 1.8% and 3.0%. We don’t know what that overhead would be in production until such a commercial implementation is delivered but we have enough evidence it is worth the effort with the current estimates and given that CHERI can deterministically prevent around 2/3 of memory-safety-related vulnerabilities [5], not to mention benefits of mitigating future unknown vulnerabilities with compartmentalisation.

[1] https://github.com/riscv/riscv-cheri

[2] https://codasip.com/solutions/riscv-processor-safety-securit...

[3] https://www.sunburst-project.org/

[4] https://ctsrd-cheri.github.io/morello-early-performance-resu...

[5] https://msrc.microsoft.com/blog/2020/10/security-analysis-of...
Or maybe you do, if screws are so much cheaper than nails.
It’s unclear whether this is all Azure services or a handful of preview or a subset of services that are only available in a few regions. I also assume that this is within the EU when it says international and not outside the EU? Does anyone know?

I know that not really relevant to the UK only requirement for UK police data, but as an EU based Azure customer I’d be interested to know whether our customer data is leaking outside the EU, because that would be a problem.
You have to compare nuclear to other actually possible power sources, not some idealized hypothetical. How many coal miner get black lung, for instance? How many excess deaths from burning fossil fuels are there? Without that comparison, it’s a bad argument.
Yep, I remember Greenpeace being staunchly against nuclear. I guess they were also against the environment.
I've done this sort of thing a few times.

- Build a small core team who know the problem in depth. You really need to understand v1 and v2 data and the mappings, as well as the functionality in each.

- Build a test system that is insulated from customers; you want to be able to use this as if it's the real thing, but to be absolutely, completely, dead certain that it will not affect live systems, and that no output from this will reach people it should not. Make sure there are visual indicators as well as logical traps on data exiting this system. Make this repeatable - you are going to use this system a lot to re-run tests. Despite the firebreaks, you will have some brown pants moments.

- The ideal is to move from v1 to v2 gradually, using a passthrough system. However, ime, this is often not possible, and at some point there will be a hard switch between systems.

- Develop migration plans with multiple off-ramps and fallbacks, and monitoring. By the time you press the switch you should know exactly how everything will work, and you should have no issues, despite this, you should have layers of contingency to allow for business as usual when the unplanned happens. This is a mix between technical and business and it should have been properly understood by everyone involved. Monitoring is critically important. Your plans should include aftercare... for example, what happens if you think the migration is successful, and two weeks later you discover an issue with 200,000 transactions. How will you reconcile? How will you communicate with the affected parties?

- Look for classes of things... Can you find 100,000 dead accounts that can be removed? Can you find 500,000 that have only ever had one transaction? Look for classes of errors - and fix them before migration. Keep a record of all of this, and make certain that you have covered all cases and all records. If you are lucky, you will be able to migrate classes from v1 to v2 and have the passthrough transparently manage this.

- Ideally, have a log of transactions that can be replayed on demand. So that you can run systems in parallel and so that in the event of issues, you can unwind.

- Keep written logs of all the things that you and the team do. You _will_ forget stuff you've done. This is true on an hour to hour basis as well as a month-to-month basis.

- Work on making migrations fast. Can you organise it so that 16m migrations take 10 minutes? This allows you test and retest. You want anyone to be able to run on-demand migrations.

- Look to the end-users. For an upgrade to be successfully deployed, both the business and the end-users must be happy; you will want to run test groups, pilots, group conversations, and make your team available to the end-users. Nothing should be surprising by the end. You will also need to know that v2 is performant - catch these problems before they become general issues of dissatisfaction. Look also for pain points and try to ensure that you remove them in v2. Change is painful, but if you can show that there are benefits you will ameliorate much of the criticism.

- Have defined end-points. You do not want to be doing this in 5 years time.
That's not the same as "not caring for who signed something" though, if you think about it: "Whoever holds the same key that signed this package" is still an identity, if a pseudonymous one.
Each core needs to handle the full complexity of x86. Now, as super-scalar OoO x86 cores have evolved the percentage of die allocated to decoding the cruft has gone down.

…but when we start swarming simple cores, that cost starts to rise. Each core needs to be able to decode everything. Now when you can a 100 cores, even if the cruft is just 4%, that means you can have 4 more cores. This is for free if you are willing to recompile your code.

Now, it may turn out that we need more decoding complexity than something like RISC-V currently has (Qualcomm has been working in it), but these will be deliberate, intentionally chose instead of accrued, that meet the needs of today and current trade offs, and not of the eart 80’s.
Historical Housing Prices Project
Right. Except the around 400 nuclear power plants currently in operation.
Preach, brutha!
> there is no string of accidents or fatalities after decades of this.

Ignoring reality

A lot of people killed on the road
If Rebel Moon and the Demolition Man taught us anything, is that even when 8bn people will be spied upon, there will be some that will object this and fight it tooth and nail.

(Oh and History teaches that)
I just wanted a tool that told me if my website was online, or not.
I love so much about that TV guide recipe insert. The border art, the Kalligraphia font of Partridge Family / Peter, Paul, & Mary fame... but damn those gelatin salads always sound revolting.
One of the datasets we evaluated against in our paper uses a bespoke capture rig (https://github.com/facebookresearch/EyefulTower?tab=readme-o...) but you can definitely train very respectable NeRFs using a phone camera. In my experience it's less about camera resolution and more about getting a good capture - many NeRF methods assume that the scene is static, so minimizing things like lighting changes and transient shadows can make a big difference. If you're interested in getting your feet wet, I highly recommend Nerfstudio (https://docs.nerf.studio)!
This. If you could make ship-sized nuclear reactors easy and affordable, the US navy would be knocking down your door. There's no lack of DoD funding, no lack of operator expertise, and no nimbyism from dolphins, so the fact that the USN doesn't have a reactor in every single Arleigh Burke is purely because it's not economical.
> Some of this movement is funded by Germany Governement.

At first I thought you were joking, but of course you were absolutely right: https://www.howsolargotcheap.com/germany
It’s interesting seeing the difference in how solar is usually talked about versus backup generators.

Whole-home generators are expensive and get used rarely but are often justified as a “just in case”. Solar doesn’t enjoy this kind of leniency, unfortunately.

Being less dependent on the grid has many benefits that get ignored over a perceived return on value.
> The less it changes the the more vulnerable it is, the less compliant it is, the more expensive it is to operate (including insurance), the less it improves and add features, the less people like it.

All of that is true, but all of that cost is being paid regardless while the legacy system goes unmaintained. When the company decides to shut down a data center, the choice with legacy systems (especially niche ones) is often "lift and shift over to cloud" or "shut it down". Notably missing among the choices is "increase the maintenance budget".

All these hypotheticals aside, one actual bonus of shifting onto lambda is reduced attack surface. However crusty your app might be, you can't end up with a bitcoin miner on your server if there's not a permanent server to hack.
AI doesn't think nor does it understand.
> and land get taken.

It's always land. This is because land is scarce. You can keep things that aren't scarce without force.

> Is there any convincing argument for getting out of this equilibrium?

The total destruction of artificial scarcity?
I don’t care if it’s good or bad, I just want it to work, and have it still work 10 years from now
This is an old trope that's not longer accurate pretty much across the board for renewables/batteries.

Also.. Mining for solar panels has never been the major energy cost. Solar panels are primarily silicon (re: sand). The actual energy expensive part for them is/was melting the sand into glass. Even the next major element, aluminum for the brackets, accounts for far more energy expenditure than the mining of the doping agents.

Even for windmills, the major energy cost isn't mining, it's the smelting the steel for the tower.

Renewable energy is a piece of the puzzle and not everything. It's a major and important piece. Switching the grid away from fossil fuels accounts for a huge portion of emissions and renewables are some of the fastest and cheapest to deploy solutions currently.
Carbon emissions kill over a million people a year. I would say that’s a bigger problem
Using compiler specific extenions isn’t really C, though. It isn’t portable and there is no specificed ABI. Add enough of them, and it might become a new language “C with Memory Safety”
I learned (recent Tales-from-the-darknet podcast episode) some people use iPhone Touch and now iPads instead of phones to avoid SIM card swapping(?) attacks. So all calls via VOIP or other apps. It apparently also makes it harder to track the device because an attacker can't rely on cell tower information.
Folders in the bookmark toolbar. Works for me, I guess.
I think it makes a lot of sense. You could probably seal the engine compartment for decades at a time.

I read somewhere that running on bunker fuel was the equivalent pollution of 50m cars.

https://sustainability.stackexchange.com/questions/10757/doe...

I think it was russia? that had nuclear powered ice breakers. Made sense as the constant power demands must be phenomenal.
There's no direct connection to the Lambda container, it goes through a load balancer. The load balancer can keep connections open for reuse.
It’s only the most expensive if you completely ignore the externalities of carbon emissions
That aside about IDTV was interesting. Hadn’t heard of that before.

It used a buffer to interpolate multiple frames from OTA TV also had motion sensing!

Wonder how good it looked in reality?
I'm confused, why would you insist on using an LLM for decision making? It's not
"the collective wisdom", it's a probabilistic language model. I imagine LLMs are better suited as a last step. I'd want a proper model to infer a decision, and an LLM to transform it to a human-friendly-formatted advice.
Here’s a simple one: if I need to say something accepts inbound 443 from 1.2.3.4, I create an AWS security group rule and will never need to touch that for at least a decade, probably longer. If I’m doing the same thing on premise, the starting cost is learning about something like Cisco hardware which costs a lot more to buy and I am now including in my maintenance work. Over a year, I will spend no time on my AWS rule but I will have to patch the physical switches and deal with primitive configuration tools for a complex networked device. If my organization cares about security, I will have to certify a ton of configuration and practice unrelated to packet filtering whereas I can point auditors at the cloud service’s documentation for everything on their side of the support agreement.

What about running code? If I deploy, say, Python Lambdas behind an API Gateway or CloudFront, they’ll run for years without any need to touch them. I don’t need to patch servers, schedule downtime, provision new servers for high load or turn them off when load is low, care that the EL7 generation servers need to be upgraded to EL8, nobody is thinking about load balancer or HTTPS certificate rotation, etc. What you’re paying for, and giving up customization for, is having someone else handle all of that.
Evolution suggests that genes with no strong survival benefit are eventually discarded.
I am also have been using PopOS for gaming.
> I’ll eat my hat if cargo ships go nuclear.

Would you like some ketchup or ranch sauce?

https://en.m.wikipedia.org/wiki/Sevmorput
Thank you. Received, sampled, I recommend.
I feel like the lighting part will become "easy" once we're able to greatly simplify the geometry and correlate it across multiple "passes" through the same space at different times.

In other words, if you've got a consistent 3D geometric map of the house with textures, then you can do a pass in the morning with only daylight, midday only daylight, late afternoon only daylight, and then one at night with artificial light.

If you're dealing with textures that map onto identical geometries (and assume no objects move during the day), it seems like it ought to be relatively straightforward to train AI's to produce a flat unlit texture version, especially since you can train them on easily generated raytraced renderings. There might even be straight-up statistical methods to do it.

So I think it not the lighting itself that is the biggest problem -- it's having the clean consistent geometries in the first place.
Funny, I plugged my ST back in today and then there's an ST article linked here.

I never had one back in the day (in fact I wasn't even alive yet), but became aware of it when my interest in the demo scene and chip music started in my teens. The ST's sound chip, the YM2149 - an antiquated PSG based design, was of course made fun of back in the day by Amiga and even C64 owners. But ironically something about the sound it makes spoke to me and I had to get one. The history of the ST demoscene is quite interesting to explore chronologically, seeing the hardware get pushed past it's boundaries time and time again as the years went on, and the rivalry with the Amiga scene is fun.

Recently I've been doing some retro coding on it for fun, setting up okami shell, MicroEMACS, and a sort of make wrapper [1] for the Pure C compiler, using some available C libraries to make a little curses-like SNDH player for myself. Of course using a cross-compiler on a PC would be simpler but where's the fun in that?

[1] https://github.com/th-otto/pcmake
And a fairly quick way to do the same sort of thing is `git fetch && git rebase -i origin/main`. You never bother updating `main` because you kind of don't care for the task at hand.
Reminds me of a court case [0] proactively challenging Facebook, due to a time the company gave someone a lifetime ban [1] for making this kind of consumer-tool.

[0] https://www.theregister.com/2024/05/02/meta_facebook_tool/

[1] https://slate.com/technology/2021/10/facebook-unfollow-every...
> In an ideal future, firearms would be banned worldwide.

But not bombs, knives, chemicals or sources of radiation?

Well.. good luck.
There's a (diminishing) correlation that shouldn't be ignored. I'm not saying we should abandon solar because of that correlation but it should at least be factored in.

For example, I think it's a dumb idea to turn every road into a "solar road" just because "who cares".
RemedyFest [pdf]
Breaking Software Bottlenecks
Cool script.

My hack is to live in a country where the local language is not my own, and not the one I have set in my Facebook settings.

As a result, Facebook rarely has advertisements that can target me, because my language has been filtered out by the advertisers.

When one does appear, it’s nearly always in the local language, so I’m kind of deaf to it and I’m not going to actively respond to anyway.

Luckily they haven’t figured that out yet, even though I’ve been an Facebook user for many years.
Does this just impact ads shown on the site, or does it also cut down on data collection and targeting that occurs when you browse to third party sites who happen to include javascript from Facebook?

How's this technique compare to just staying logged out of Facebook? Or using it solely in a sandboxed browsing environment?
You make the plasma before any fusion can happen.

Just there being plasma there means nothing, you inject it on the machine already that way.
George Gammon made another video 21h ago, in which he explains it in depth[1]. Then again, i don't understand that situation with the financial instruments, and indeed it may not have been wise of me to mention it.

In the broad economy however, any protectionist regulation, any anti-monopolist regulation, any protection from myself like narcotic laws, and a myriad of other things, creates bubbles.

In the economy, following Adam Smith's invisible hand, any decision not taken by the individual, but is imposed upon him, and this decision carries along with him a financial cost, creates bubbles. It is that simple.

When an individual wants to hire an Uber instead of a cab driver, there are certain factors influencing his decision, like cost, convenience, quality of service and more. When an individual wants to hire an Uber but he can't, then the inferior product or service will continue to be profitable, until the individual finds a way to get around the laws and regulations.

When that happens, then the people who offer the inferior product or service, lose their source of income in a moment's notice. That's when the bubble pops.

The bad situation here, is that a lot of people will lose their source of income all at once, instead of it being gradual. That's why creating bubbles is not advisable, and it creates explosive and dangerous situations.

In Uber's case in Greece, they are banned somewhat, because as a company they have revenue from Greece, but they don't pay taxes here.

[1] https://www.youtube.com/watch?v=0S3NLXBjJdQ
You can get a similar effect with Azure App Service, which is basically a cloud hosted managed IIS web farm. A web app is “just” a folder and takes zero resources when idle.