skysight-inc/HackerNews huggingface dataset:
I did justify my statement, but I will say it again. Solar project development is an exercise in value capture. As long as solar is cheap enough to compete in energy markets (which is currently the case), when some development costs go down, someone else in the value chain will try and find a way to increase their slice of the pie to try and compensate.

A good analogy is landlords. Why do they raise rents instead of decrease rents? Because they want to profit, and because their costs increase over time due to inflation, and because the market will let them.

Here is another fun one. What happens if/when interests rates go up? We are at record low rates, and most solar projects are debt financed? How will higher rates impact project costs? The obvious answer there is that costs will go up.

> In the US, for example, land can be < 1% of the cost of a utility-scale PV installation.

As I mentioned, that is the case now, but it will likely not be in the future. The number of sites close to existing transmission lines, with good geographical features requiring minimal grading, low flood risk, low wildfire risk, low hurricane risk, etc... are going to diminish quickly as saturation increases. And when it comes to land, costs can go from reasonable to painful real quickly.

I am certainly rooting for costs to go down, as I think that is better for humanity. But I am not betting on it. Why do you think they are going to go down? I don't think you have made a good case for lower costs other than that is what has happened in the past.
Yes! Because we support the API so users can customize the usage. Now we support extensions including MarginNote, Kindle, Notion and iPhone shortcuts.
One contest I'm aware of accidentally had the organizers kid win the contest. Who would have thought it possible? I feel really bad for the one that actually deserved to win.
Wow this really brings home how recent it was still in the scheme of things. I had it in my mind before this thread and article that Babbage was in the 1600’s or something.
company's
Allowing or banning fracking is pure politics.
The etrade breakage was a failure of the previous detector, which expected an encoding declaration within the first few page KB and introduced a page reload otherwise. Switching the current encoding manually does not reload the page per se.
> It seems to be a lame argument saying somehow high energy prices no longer affect US consumers.

From the article:

Now, after the shale gas revolution of the last 15 years, the impact is more subtle. Higher fuel prices disadvantage consumers and energy-intensive industries, yes. But there is a counteracting surge in incomes for domestic energy producers and their workers.
It breaks things without possibility of repair for a certain group of users. How is this not an issue?
iOS. I use Safari and adguard. It supports custom block lists.
An Invisible Chasm
Archival platforms not based on fraud or deception are far preferable.

Internet Archive or Archive Today.
Isn't interface{} similar to void * - the king of hiding types?
Chinese Fountain Pens of 2022
The quick option was already there before though - it was labeled "automatic" before. The only thing he did was remove all other options.
The deepest inheritance chains I saw in practice were the OOP GUI programming toolkits, they'd go six-seven deep and invariable started needing to clone logic to avoid diamond issues (they were always single inheritance it seemed).

Honestly OOP did a lot better in those than the procedural toolkits they replaced in many ways. It was generally "better".

So if we're going to dump OOP for ??? I would say that a really amazing GUI toolkit that is pretty clearly better than the classical OOP inheritance model would really underscore the point. I can see a compositional interface GUI toolkit that is great.

I have since those days not done a native UI, so all of the modern ones, from KDE/Qt, GNOME, whatever the hell replaced MFC on windows, etc I am clueless about.

Plus all UIs are kind of dominated by HTML/CSS/javascript style of code, which is its own special evolutionary tree at this point.
Yeah, I think the main contribution of this paper in the long run, might be that the time is right for optimizing the controller together with the hardware?

I'm imagining optimizing the plasma configuration, reactor shape, coil/sensor placement and controller all in one giant computational optimization. All the algorithmic components and models humanity needs to attempt this seem to be there.
I agree, of course! But I'm trying to get at a different question: what sort of processes can be expected to give better or worse answers to the resource allocation problem?

This probably can't be answered at HN comment length. Or at book length, for that matter. But I will say that I think letting individual rich people unilaterally jump on causes that they believe to be important and neglected seems like the kind of thing that will probably give better net outcomes on the margin under systems like the one we currently have.
First time that an investigation is able to tie Turla to the FSB
> Don't be afraid to schedule a synchronous communication session in whatever flavor you prefer.

That is its own separate problem. Constant distraction in Slack, followed closely by Zoom call hell because you didn't respond fast enough in Slack and wouldn't it just be faster if we all got on a call?

If we're going to leverage the power of remote work, part of that is re-learning how to do effective asynchronous communication and not succumbing to interruptions just because it's so easy to inflict them.
Right, but I'm challenging the notion that use means usefulness. I don't think that can be assumed to correlate without further justification, especially given the ease of producing counterexamples and scenarios where this is not true.

Some features are used a lot because some other features are inefficient. Sometimes a feature is very useful in some rare situations (compare with seatbelts).
That comment was probably deemed to be unsubstantive - you replied "no" to a lot of stuff without explaining why you were disagreeing with it. (I would have just downvoted that comment, not flagged it - I only flag comments for serious policy violations like incivility, spam, etc.)
Indeed, and unfortunately my mind will forever work this way.
Cool, can't wait for anti-bot protection to start rejecting me because I use firefox.
I've found that the Kindle app is surprisingly good at reading comics. Pair it with a tablet and Libby and you are good to go... at least as a casual reader.
But this benefits absolutely nobody. Not even the manager doing that. I know that in my workplace a manager would get chewed out for that, as this practice is explicitly banned by policy. Any issues should be raised the moment they are discovered.

Even without the said policy, it doesn’t benefit the business, because if it’s a problem employee, you’re pointlessly keeping them on a payroll, and it doesn’t benefit the employee, because if you hit them with everything at once, little of it will resonate with them.
> - Since the process produces magnetically charged plasma, steam turbines are not necessary, a solution of directly harvesting energy with electromagnets was proposed.

But wouldn't that require aneutronic fusion to be viable? I had thought that the prevalence of neutron radiation otherwise would have made directly tapping the plasma for electricity impractical.
Come work with me ;)
Any chance you work on MS teams?
> Because you, in debating the exclusion, chose to debate the relative merits of broad topics rather than specific articles. The reference wasn't general, it was to the specific thread.

I'll take "Weasel Wording" for $800, Alex.

As for your advice on challenging flags, the motive is certainly there to follow this procedure:

1. Flag a submission early in the morning, before anyone's had a chance to vote on it.

2. Commenting is unavailable to most people for most of the day.

3. If and when it gets unflagged, everyone's moved on.

4. Enhanced downvoting!

If you say no one's doing this: be transparent and prove it.
The Pentagon wants to use Starship for military transport. Getting troops anywhere on earth within an hour would be a huge advantage.
See this issue: https://github.com/golang/go/issues/26520
That's my point. We should vote, we did vote, and we legitimately came to the current allocation. If you disagree, feel free to persuade us to vote differently, but don't tell me I have to give up my vote and do what you want.
I'm tired of constant chatting.

Slack encourages quick, stream-of-consciousness, short responses. Plus, it's hard to find past discussion, and it's hard to jump in after being gone for a few days (or, even a few hours).

Threads are absolutely the answer. But, the defaults matter - Slack isn't encouraging threaded, long-form messages. Instead, it makes all messages feel urgent - and it makes the cost of sending a message way too cheap.

I'm on a mission to bring back forums, where threading is the default. Inspired by YC's Bookface software, I'm working on a project to make forums as slick as Slack or Notion [1]. I think that long-form discussions and slow notifications are the key to bringing sanity back to discussions. And, I think the key is one amazing email summary per day - and few (if any) other notifications.

If you're interested in this problem - please reach out!

[1] https://booklet.group
Here you go: https://github.com/golang/go/issues/26520
I've got nothing at all against motorcycles except for the idiots making noise.

If they're willing to take on the risk of riding around all these distracted idiots in SUVs, then more power to them.

I'd like to ride a motorbike but I just wouldn't feel safe considering how many close calls that weren't my fault that I've had in the car, despite considering myself a defensive driver.
Running `cargo tree | grep -i ring` shows ring v0.16.20 a whopping 7 times in the s2n-quic repository, so it's somewhere alright.
Yes, but it's a bit like Rust's `unsafe` in that reaching for it first is not a great practice. There's usually a better way.

Using interface{} where you truly don't know and can't predict the data being sent to you is mostly something that libraries (like encoding/json) have already handled, so I don't have to interact with it much directly.

I think generics are going to have the biggest impact in adding effortless type safety to all kinds of libraries, though.
Well I don’t really agree with the premise of your statement. I think that the benefit of the new protocol is going to mostly be felt inside the data center.
Just to nitpick, there were two Falcon Heavy missions in 2019 - Arabsat and a DoD one. That's after the successful demo launch, which was in 2018.

There are also some number scheduled for this year - I doubt we will actually see five Falcon Heavy launches, but there will be a few.

Falcon Heavy was a victim of Falcon 9's success, but it probably can't do the same thing in turn to Starship, it's just too expensive.
Keyword being almost all. I ran `cargo tree | grep -i ring` in all four currently listed QUIC implementations, and three of them have ring somewhere in the dependency tree, except for mozilla/neqo.
Why the Calorie Is Broken
The point of the example is that there are things that are useful even if they are not frequently used. You simply cannot equate use with usefulness.
> IMHO a manned mission to Mars makes almost zero sense.

Whether it "makes sense" or not, there are a lot of people that want it to happen, and it also happens to be the express purpose of SpaceX and Starship. That's it's raison d'etre.
>The intended meaning is pretty obvious, and explicitly laid it in the second paragraph.

Is it? As a native English speaker, the only thing that was immediately obvious (to me) from the title was that commit != getting away with.

If I ever decide to read TFA (highly unlikely), I'm sure I'll notice that part. Thanks for giving me the heads up though.
> all happening in the open on a bug tracker!

I find it suspicious that there was not a single comment from a user before the change shipped - but immediately after, there were various complaints. That's not the first time I see this pattern in a bug.

This looks more like the "Hitchhiker's Guide to the Galaxy" definition of "open" - where the discussion is technically public, but you heavily rely on the fact that no one knows it exists.
Developing Time Crystals for Use in Real-World Applications
> A practice that was already in place was one of diligent threading – not only was threading encouraged, but by strong convention, every topic goes into one. We thread like our lives depend on it.

This is describing Zulip. And indeed, Zulip is excellent. The only downside is that the mandatory-thread paradigm makes it difficult to find the appropriate place to deliberately fuck around, which is also a valid mode of human socialization. But if you want to get work done, use Zulip, not Slack.
Well fission energy would be much cheaper if most of our energy was produced that way. Economies of scale provide huge opportunities that are currently limited by political will. I don't see a reason fusion can't quickly become a large scale source of power, because unlike fission, there would be much less political backlash.
Isaac Newton’s life was one long search for God
Reminds me of Elon’s long game of naming the Tesla models S3XY…
I had a “drunk” parked in the inside lane of the four lane road in front of my house one evening. He was just stopped in traffic and got out stumbling around. I was annoyed (naturally) and he handed me his phone. Whatever, dude; I don’t want to talk to your friend right now. Somehow he insisted and his friend told me he was diabetic and to call an ambulance.

I did, got him some OJ, and moved his car out of traffic. He went from incoherent and “drunk” to “seemed pretty OK” in just a couple of minutes before the medics even arrived. (He still took the ride, but it was none of my business at that point.)
Extreme weather will be far more noticeable than that amount of sea rise over 3 decades (if no less). We are not good noticing slow changes, but a hurricane hitting a big city, a heat dome or an atmospheric river drowning a populated region are things that will cause alarm, specially if that kind of things happens frequently.
Unicode encoding was far from universally adopted in the early 2000s. Some legacy content will always exist, and the moment where dropping the feature is harmless is also the moment where there's no reason to drop it in the first place, since it only ever comes into play with broken legacy content; otherwise, it is entirely hidden and has no harmful effect whatsoever.
I've been paying attention to [flagged] posts for some months now, to see what [flagged] means in actual practice. I've seen no correlation between the presence of [flagged] and the relative informativeness of the submission or volatility of the comments. So I think [flagged] is just noise.
It's a stretch to say will always have to.
I recently installed Slackware 15/Plasma on a Thinkpad. It "works out of the box, is well supported, and lets me get on with things." No tinkering was needed.
A better argument would be whether there are any restrictions at all that, during a world shortage, would prevent companies producing oil from exporting it to other parts of the world to the detriment of local US consumers.

There aren't, so the US isn't independent on anything: the regular citizen will get priced out of the market regardless of their need the moment there's profit to be made elsewhere.
I think you need a fission reactor to get the tritium.
Unicode encoding isn't what I was referring to--it was the ability to specify <META http-equiv="Content-Type" content="text/html; charset=EUC-JP"> (copied from HTML 4.01 specification, dated December 24, 1999). That might not be the first time it was possible to declare the charset of an HTML document within HTML itself, but I don't see any mention of it in HTML 3.2.

Also, it's wrong to say that there's "no harmful effect whatsoever"--the ability to do charset overrides requires code to support it, and that code could force awkward compromises in (say) your HTTP layer. All features have costs, even if they're invisible.
“Should” is not “is”. As a user, I run into broken sites regularly enough. I still want to be able to see them. I get the “let’s bury all broken legacy and hacks as quickly as possible” mindset, but when it comes to the issue of the main text of a page being unreadable, I think there is a high bar.

> older sites should fix their sites.

A lot of the reason they are considered “older sites” in the first place is because they are not heavily maintained. The thing to remember about the web is this: not all websites are “software” that is maintained. Some of them are static works similar to a movie, with static content.

> The single-byte Latin scripts are semi legible, so that is enough for me.

Did you see the example that I gave of Polish text? I am sorry, but if you feel like reading multiple paragraphs this way is bearable, then we will just be stuck in disagreement.
> but that's just going to take a long time, particularly if F9 is, say, sub-$15m per launch.

1) SpaceX isn't a public company; among other benefits, there's substantially less pressure to maximize profits.

2) Starship launch costs don't need to compete with F9, they only need to compete with the other competition.

Also, it's worth repeating that the goal of this entire endeavor is reaching Mars. The above state of affairs isn't a coincidence, but a very deliberate part of Musk's plan. (Also, luck.)
Havent had a chance to play that but I thought Prey was extremely underrated. Also hard as fuck on the harder difficulties however. Reminded me of a modern remake of the original Half Life on crack
No, it's because the transfer orbit with the largest payload for the thrust is only available in a specific configuration of Mars and Earth, which only happen every 26 months or so.

Note the spacing for launches for Mars missions:
https://en.wikipedia.org/wiki/List_of_missions_to_Mars
Building one power plant is incredibly expensive. Building it again costs less. Building it 1000 times costs much less per plant. We're not building thousands of fission plants because of politics. Fusion might be an easier sell.
>A CGM can cost $400 a month

What in the world? $5k a year? How on earth are those things so expensive? 2 fully spec'd macbook pros per year? Surely they aren't that complex. Am I missing something?
Though not as large, there's also a standing Saturn 1B at the Alabama Welcome Center in Elkmont on Interstate 65.
I’m interested in your idea, bringing what we’ve mastered in chat to the forum, but I don’t want to give my phone number or spin up a forum just to see. Is there an example forum?
The chart links to the EIA article ... so that is the source, but I don't know how high quality it is.
Yeah, the tslim X2 would be the preferred pump at the moment, but by the time he gets old enough for a pump I hope the technology will have improved a lot.
You can already do this if you’re using cellular internet and not Wi-Fi under Settings > Cellular and then turn the button off for a specific app.
I have few more things to add...

1. There is one specific "addon" developer/employee who wraps opensource docker containers and automates the releases through github release builds and proceeds to link the about page of addon to his donation page. Example: Nodered, InfluxDB, AirSonos/Cast addons in HA have no link to actual projects or their repos.

2. Absolutely have no standard for stability for what should be critical software, just check the number of production releases to end customer devices this month. EIGHT, yes they pushed eight releases to core app to end users, that's beside the "addon" updates that the guy does with his automated releases.

3. Thanksgiving week of 2021, they pushed a ZWave update which the guy rewrote how events are processed and proceeded to brick everybody who updated.

4. F*ckin forced OS update, the developer refuses to be able to turn off forced HASS OS updates. If you block the update hostname on your router the stupid script to check updates goes crazy and starts eating up CPU.
That's a big business card. :)
> or they seem to contain false information

I don't agree with flagging comments just because someone thinks they're false. I'm guessing that many things that the majority of people on HN consider false at a given point in time are actually subject to serious debate by knowledgeable people. For example, statements about Covid being primarily spread by droplets, which were made by the CDC early in the pandemic and were later shown to be false. If someone would have posted a comment back then saying it's more likely that Covid was spread by aerosols (which is what the CDC says today), should it have been flagged?

"Facts" in news stories are frequently proven wrong as more information becomes available.

If you think something is false, it's better to cite a reference that supports your position. Perhaps someone will cite a more convincing reference that disputes it, and people can delve further.
Not the person you're replying to, but in general refraction is pretty easy to do in a ray tracer. When the ray hits the object you use the normal vector, the incident ray direction, and the index of refraction of the material (or materials, if you're transitioning from one substance to another with different index of refractions) to calculate the new ray direction and continue from there. Usually there's some amount of reflection, too (the amount varying based on the angle of the incoming ray with respect to the surface), so you might spawn two rays: one continuing through the object, and the other bouncing off.

What's much harder to do is simulating the light that's refracted or reflected off of objects (called "caustics"), like the light on the bottom of a swimming pool. To do that in a physically correct way generally requires falling back on some kind of global illumination technique like path tracing or photon mapping.
The transfer and the new address will be easily visible to anyone watching the original sanctioned address.
if you control the client/server in these situations in might be worth just using HTTP/2 instead of QUIC for these networks. just write your protocol assuming 'streams' exist and then have a HTTP/2 and a QUIC implementation. this is what cloudflare does with their cloudflared tunnel.
You have created an expert system for HN comment threads implemented as a browser extension and with a knowledge base encoded as keyboard shortcuts.

Now all you need to do is to use machine learning to learn the shortcuts, and then use them. Then you will have automated half of your job :P
Seems almost criminally negligent.
This is awesome! I should have put something like that in there, but I wouldn't even have thought of the dithering, and since I don't know much about graphics I didn't know about Reinhard tone mapping.

There's an interesting thing that happens where sometimes if you constrain yourself to 1% or 0.1% of the code you would normally use, you end up getting interesting uncontrolled effects. cf. http://canonical.org/~kragen/bytebeat
I read a story once, which may be apocryphal, about various intelligence services switching back to printed/typewritten records for incredibly sensitive stuff to avoid the possibility of it leaking without having planted a spy.

It seems unlikely to me, but I could imagine situations where that level of concern might make sense.
To people thinking that this was removed gratuitously please read the bug and linked bugs carefully.

This got in the way of implementing various improvements to <meta charset> and interop improvements to XHR.
Climate change disproportionately harms poor people. Environmental degradation in general disproportionately harms poor people.

Everything disproportionately harms poor people. It's practically the definition. To be poor is to have little power. So for any X you have less to bring to bear to avoid it.