skysight-inc/HackerNews huggingface dataset:
Just remember that a huge part of the current excess cost is in part:

(a) because nuclear power is the only energy technology for which the full lifecycle costs have to be fully accounted for upfront. No one is accounting for the disposal costs of solar panels in their initial capital expenditure, for example.

(b) The build costs in terms of energy of wind and solar are comparably high. They are raw material and energy hungry and have a much lower energy return on investment and require a much larger geographic footprint. Plus their use without adequate baseload generation will necessitate a large additional requirement for raw materials to create energy storage. Much if not all of wind and solar’s cost advantages will likely evaporate in an environment where they are no longer subsidized by very cheap fossil fuels.
They already have that with ISPs, right? I don't see this as worse. If anything ISPs are more scummy.
Apparently they are using technology developed at the Pacific Northwest National Laboratory[1]. The US government owns the patent. However, Gary Yang, the lead scientist on the project, could not get industry to develop it, and licensed it to a Chinese-Dutch company.

1:www.theregister.com/2022/09/30/chinese_battery_vrfb_us_patents/
ReScript was advertised to be a great language for powering up React in the years of ReasonML. It may be opinionated, but people grew interest in ReScript along with React.
thanks your reply, I did not find if this only work when they just want to offer some gifts.
There really isn't that much to it. E.g. in Python you can just use a dict.

# (state, event) => (next state, action)
FSM = {}

Add transitions (using enums):

# Simple left down-[move*]-up sequences.
FSM[STATE.clear, EVENT.left_down ] = STATE.set_caret, 'set_insertion_point'
FSM[STATE.set_caret, EVENT.left_motion] = STATE.set_caret, 'set_insertion_point'
FSM[STATE.set_caret, EVENT.left_up ] = STATE.clear, 'nothing'

Then when an event happens you drive the FSM like so:

new_state, action = FSM[state, event]

Check out https://git.sr.ht/~sforman/Xerblin/tree/trunk/item/xerblin/g... for an example.

There is also a DOT file (and SVG image) of the resulting state graph (the code to generate the DOT file directly from the FSM dict is at the bottom of the mousebindings.py file.)
YES so much this. It's really not hard to see why so many people are doing resume driven development, everyone is overworked and understimulated. Nothing matters, the business doesn't care about good engineering, there are so few interesting problems, ugh.
Did IBM deploy mainframes to universities for academic purposes? I started college in 1989, and it was fully micro. We learned Pascal on 3B2 systems running SVR3. There was a VAX running 4BSD that was designated as the students' playground. I learned assembly on Apollos running DOMAIN/OS, I think, and then there was a lab full of brand-new diskless SPARCstation ELCs.

I guess some BITNET buddies might have been on VM/CMS, but I think even our student bookstore avoided selling IBMs; they had Macs and NeXT stations on the showroom floor.
Fuck, HTTPS was already popular by the time I went to college. That explains everything.
The dream of consumer AR is dying slowly. It's a disruptive tech that's gone into sleepyland.

Look at stable diffusion as a comparison, blows everyone's mind every day for 30 days, moving at an incredible pace, and for free...

Sure hardware, vs. software but still, we're in different leagues.
There's certainly something to this, but the analogy seems stretched past breaking on a few things.

Also, do we really know that Google search is worse than 10 years ago? I mean I'd say it is worse, but I'm prey to all the cognitive biases.
No one is forcing you to use TLS. Do whatever the fuck you want, it's your site?
This is awesome! My only feedback would be to also add the typical symbols used in jazz worksheets for diminished, major, etc, instead of just the name.

Great work!
If you are OK with moderately high bitrates, you might prefer something simpler like an ADPCM scheme. It's pretty damn easy to implement ADPCM, certainly a lot less math heavy than MDCT-based schemes, and they achieve good quality at a somewhat higher bitrate (I have no data, but I'd guess 200-250%~ish.)
>Have you heard of inheritance?

A powerful businessman living forever isn't the same thing as inheriting his son. Children rarely follow in the footsteps of their fathers. What if Warren buffet lived forever, for example? He's very good at saving money and investing. He'll eventually just have a large portion of the wealth that exists
What was state of the art tech before the 914?
Yeah, it doesn't have to do with nationalized gambling. It has to do with strict sweepstakes laws.

* Register the sweepstakes rules and all advertisements used to promote the contest with the Quebec government at least 30 days ahead of the sweepstakes' launch.

* Pay a fee of up to 10% of the sweepstakes' value, depending on who is allowed to enter.

* Offer the sweepstakes rules in French as well as English.

https://www.liveabout.com/why-are-so-many-competitions-void-...
Forwards and backwards compatibility and not having to rely on every vendor to ship support for the codec you want to use in your software.
Tesla Optimus Bot
We need this because we are a nation of laws and punishing legal immigrants who scrupulously adhere to the law is an affront to our notions of fair play. H-1B holders are among the most educated and highest paid people in the country, and are a huge net-positive for the country. There are hundreds of rural counties where they are practically the only doctors who provide care, and there are scads of industries that will be thrown into disarray by turning them away. It’s better to encourage immigration from people who speak the language fluently and can integrate into American society better and practically immediately, than to throw the doors open to poor uneducated people who are mostly here illegally, break dozens of laws everyday merely by being present here illegally, and are likely to remain an underclass for generations irrespective of how hard they work.
This is what happens when you have "intellectual property". You were warned, but noooo, people had to own ideas forever.
For some reason I just remembered that Simpsons episode where Homer designs a car.
> If such new players with win streaks far above than what is to be expected by their level ranked up very fast (and if they are not that good, get thus "picked apart"), smurfing "to have fun killing some low-level players" would be impeded by a lot.

That just tells me you haven't had much experience with this. You are correct, if they keep going on those massive win streaks, they will grow out of that new player MMR soon enough.

You know what's the simplest and most common workaround to this? Just tank a few games in a row intentionally by doing nothing or playing poorly on purpose.

It is even more annoying to deal with than with someone who is tearing through low MMR on a massive winstreak, because you can at least theoretically (but unlikely) beat those players. Cannot really win a game when your teammate plays poorly on purpose or doesn't do anything at all.
Shocked that these well funded incumbents don't have to continue to innovate or secure the castle
Because it is visual noise. It's really hard to track, especially on the CLI. It's also a lot easier to reason about the codebase through time if it's basically a linear track.

We started off with merge commits and moved to squash rebase (team history to team clean), and I gotta say, I absolutely love team clean in the overwhelming majority of cases.

The only time team history is handy is as a sort of temporary space on feature branches where you are sorting out complex merges, debugging, or trying different patterns. But all of that gets squashed away onto main eventually.
Hmm, I don't know whether that applies to H4CK1NG G00GL3 or just to the main CTF (which took place from July 1 to July 3).
> I'm not aware of sub-state-machines as a standard concept.

Hierarchical State Machine.
Oh, yeah, that whole thing is maddening. Oracle is a major user of Linux; they could have just made the ZFS code properly, formally GPLv2 compatible and merged it in and overnight have an amazing storage system in OEL. Instead, they just... sat on it. Ugh.
You just need to find a small spanning set of concepts for all of human experience and then just train the decoder on those.

(I'm being serious but do not have time to elaborate as I normally would on a serious comment).
Easy come, easy go. We made great returns since 2008 for doing absolutely zero work except buying index funds and letting it ride. Nothing goes up forever, we'll probably give more back in the next 12 months, or not, nobody knows and that is beautiful.
Although it would make a good art piece at a campus
I share the exact same sentiment because using a wrist wrest for a year actually gave me carpal tunnel. Just like how it's cautioned about in this article.

I was using the wrist wrest the wrong way, however, just about everyone marketing wrist rests shows them used the wrong way, so it's a bit more than just "user error" at play here.

As the article goes into, the best way to type is with hands hovering over the keyboard. I accomplish this by using a chair with high adjustable arm rests. If the arm rests can pivot inwards like on the Herman Miller Mirra, then a standard keyboard will do. If the chair's arm rests are only height adjustable, then I use a split ergonomic keyboard. Either way, my hands are kept floating above the keyboard.

If I did still use a wrist rest, I would have it spaced far enough away from the keyboard such that it would effectively be a forearm rest. Doing so would use up more desk space than I'd be comfortable with, hence why I skip wrist rests entirely.
Right? Kids need to learn to communicate without profanities. If they can't do it, then they are going to have far worse problems and likely already do.
When I was a kid, a really good pc(like an Alienware) was 3200. Now my phone is more powerful than most of those PCs from back then. I think you'll see continue to see prices fall over time until adoption takes off
When merge commits involve conflict cleanup, they are very hard to debug (at least with standard tools like tig/gitk/diff; there might be something more advanced). I've seen lines of code disappear into nowhere in merge commits. You can only hope the conflicts were resolved well.

Even conflict-free merges can be scary -- you're trusting the system to find the right context. Of course, the same errors can happen on rebase, but at least the resulting commits can easily be inspected.
I'm reading your comment on my screen, OR AM I?
This is the way to go. I have taught teams to use state machines a couple of times, and it is so useful to just write down a list of all the events that could possibly happen. The user types something, they click on something, an api response arrives, and so on. Figuring out the list of states can be harder, so I usually start with the most obvious and draw the graph as we fill out the matrix. Usually answering the question of what goes in any particular cell is easy, and with the graph it is often easier to see when you have to add a state rather than go back to an existing one.

The best result was the time we spent an hour at the whiteboard, then the team split up and we each re–wrote part of the code (there was message–passing between components involved, so we just each took one component; I had cleverly used the events between components in the state machine in addition to external events). We all committed by the end of the day, and the next day QA said it was perfect. (Eventually I think some automated tests got written, but whatever.) Compare that to the prior months where QA would find some weird problem, someone would debug it, write a patch, and declare it fixed without realizing that they had broken some other edge case. There were never any bugs found in that thing ever again.
A sysadmin would use the logging facility (if traditional syslog) or simply awk/sed to process the logs into different files that are similar to each other (such as different levels of INFO/WARN/ERROR); then, increase the size of the DEFLATE dictionary used for compression until you get better compression.

See for instance this discussion of creating a custom DEFLATE dictionary: https://blog.cloudflare.com/improving-compression-with-prese...
What kind of job has no other measurement for output than time spent in a chair?
> but I guess it is possible they somehow have been oblivious to all of this the entire time.

It's possible their licensing lawyers have a long todo list and researching what to do with Ubuntu is not the highest priority yet. It took them quite a while before they started contacting companies about the virtualbox extensions usage.
You can bleep the swear words out, or mute them and put some funny content over it.
>We see the same process with urban tunnels and big military procurements. It is all perfectly legal. It is probably not fixable.

Not being a lawyer and all that, would some of this holding of the hands-out not qualify as some sort of grift or worse? Are there not laws already in place for this stuff? Is it a case of it being too hard to prove so no prosecutions are brought?
How is Audio encoding the most limiting factor in a VR project? :o
Afaik Opus encoder eats something like 30-50MHz of one cpu core.
Where are you getting two hours a day for yourself? We have two hours a day between kid bed time and our own, and we spend it being exhausted or together (or else we'd be total strangers real soon). I'm happy to manage 2 hours a week.
I mean, it's pretty easy to tell yourself google maps is a social good (because there are lots of good arguments that it is!).

Similarly, there are lots of reasons why improving the security of google is a good thing _even if_ you think google itself is evil.
ImpulseSV, GoodTimesWithScar, Grian, PearlescentMoon, BDubs... most (not all) of the Hermitcraft gang are PG.

Oh, and Skizzleman. Actually, Imp & Skizz's channel is great all around.
People said exactly the same thing when gasoline cars first came around.... there will never be enough gas stations in enough locations for everyone to switch over from horses...
To be fair this needed HTTP and WPA(?) lol. Old school wifi let you see everything every other client sent.
When it came out 34 years ago, it was a shockingly modern (though completely TUI-based) development platform for what these days we call CRUD apps.

I worked with AS/400s in the mid-2000s. I don't regret my time with it, but doom was on everyone's lips even back then. The main use case of the system was replaced by J2EE in big corps, and LAMP stacks everywhere else. IBM didn't particularly see this as a problem, since the WebSphere (J2EE) brand was doing fine.

As I recall, IBM's plan for the future of the ecosystem was basically to push training courses in community colleges. Probably they assumed it pointless to compete for the same pool of developers who would bolt to Facebook or Google as soon as they could get an offer.
I find the Auth0 acquisition to be more impressive. Many people (even non-tech) know about Citrix because of Windows. Almost no one outside of tech (and many people inside tech too) knows anything about auth0. Yet, we have a company that was acquired for 6.5 billions of dollars.
Out of hundreds of cars, so hundreds of spots. The six spots are dedicated to people with charges and you have to move your car to another part of the structure once you’re done charging.
Your games are different from mine, it seems
To be fair, complex is solvable compared to complicated. You just break each of the complex steps into components that are easier to solve individually. This is part and parcel for software peeps.

As stated does sound a bit pompous, but at the core, it's not inaccurate
I think the simplest one I ever did was basically a reimplementation of setTimeout in Javascript. It was really only intended as a demonstration, because of course setTimeout is right there, but with only a very slight extension you can save the time you’re supposed to activate to permanent storage so that you can set long timeouts (hours or days) and they still fire correctly if the user leaves the page and returns later. And the code is clear and obviously correct, and now the reader has some idea of how to use the code to create more interesting state machines.
Scrolling up, the same sample put NPM use at 65.17%, so I feel pretty comfortable calling it sample bias.
A lot of developers dont even realize how fast a web page or text editor could be. When you starting point is a massive farmework, you dont even realize that a computer should be ablr to fetch, parse, render and display in milliseconds. For example: the modern reinvention of serving html from a server as "server side rendering".
coffee shop hacking is usually done in an automated, at-scale fashion, often with a remote device that doesn't require an operator to be present or paying attention.

It uses lowest common denominator tactics. This VPN strategy is precisely for the lowest common denominator.

I don't understand how something can feel like snake oil when you haven't researched your own questions. I can sow doubt on anything; is it always justified?
If you have a Git repository with merge commits that merge changes back into your main branch, all you have to do is "git log --first-parent -m" to get a log that looks exactly as if you had squashed and rebased every change.

I'm surprised I don't see more people talking about this option. Sure, the syntax is inelegant, but it seems like it gives you the best of both worlds: you can browse your history as if it was linear, and drill down to the individual commits in a branch only when necessary.
Yes, the OP is the last in an entire trilogy of articles discussing this issue in detail.
How do you suppose that is? If a species were completely able to avoid the effects of aging (including age-related diseases and degeneration) what evolutionary reason would there be for death at such an early age. Especially in the case of mammals, the process of rearing the young is a large investment of resources which takes a long time to produce a return. Surely it would be better to minimize that expenditure and have members of your species who've had time to learn from their experiences. If population were to become a problem, there are already plenty of instances of species killing their own for various reasons so some form of population control doesn't seem to be an entirely unexpected adaption. Sure there may have been other things that were more prescient at the time such as disease, lack of food, etc. But I don't see why not aging would be evolutionarilly unfavourable?

I'd split things into 3 cases: (1) aging is something for which there is a strong evolutionary pressure, (2) aging was dominated by other factors and is more or less indpendent of evolution, and (3) aging is something that is strongly unfavourable in evolution. In case (1), it may be that there are strong genetic mechanisms for evolution which we cannot reverse without changing genetic data. In case (3), we have to ask the question of why we age, given evolution has worked against it. If there were some compound that could prevent aging significantly, why don't more of us naturally produce it. Case (2) is where I'd expect the problem to be the most attainable. The existence of certain compounds that seem to alleviate aging significantly might be interpreted as evidence against the third case. If such (often naturally ocurring) compounds exist, then why don't we produce them? Of course, more evidence would be necessary to say anything conclusive.
hmmm, I've never thought about magnitude being signed or unsigned. Is it little-endian or big-endian I'm now wondering
Think this in a jokingly way: since only smart and dedicated people can master Rust, software written by these people must be good most of the time. Just like how literate people in ancient societies are mostly elite class. You don't expect a peasant to write a history book.

Of course, same as how our societies develop, when Rust inevitably become more popular, this perception will no longer hold. One day, Rust will join amongst C and C++ and become tool for everyone. Until then, "Written in Rust" is just a cheap but effective differentiation ad.
Congrats on the release!

Long live simple, non-proprietary, open editors which can be extended infinitely: Emacs & Vim (and their derivatives) FTW.
i can guarantee you that requiring a wired connection for ranked matches would do far more to improve your experience than any kind of blizzard panopticon scheme will.
These kinds of rules are never applied strictly. Content moderation is always discretionary. If you don't want to be judged as adult content then play it safe, which includes censoring the f-bomb. It's just common sense.
Looks like it has been running for 20 years and is community operated? From the headline I misinterpreted this to be a commercial cloud.

I used VAX/VMS and VM370/CMS in the 80s. I have fond memories of VAX/VMS and still log in to the machine at the computer museum to play dungeon. Would also program Lisp or so, but have not figured out how to transfer files.

For IBM my feelings are more mixed. The VM side was certainly what the rest of the world got only 30 years later. The CMS side felt already a bit obsolete then when you could run X11 on a Sun.

Have never used AS/400, but from all what I have heard it is horrible even compared to CMS.
Ah, then I misinterpreted the post I was replying to and we are in agreement.
> It's really hard to track, especially on the CLI.

git log --first-parent --max-parents=1

Now you don't see merge commits.

Forbid merge commits with conflict resolution, and you're done.
The Golden Tearoom (1989) [video]
Are you under the impression a movie theater won't let a child into an R rated movie when accompanied by a parent? Because they certainly will.
I initially thought the title referenced dating someone with a job title of "task managers".
Nord Stream Attacks Expose Vulnerability of EU Infrastructure
I would say if you know that you can sell and code then go solo otherwise find partner.
I'm not super familiar with it, but I seem to remember using the `ucontext` library in my college OS class in a way pretty similar to this. If I recall correctly (and was using it correctly at the time, which is itself potentially an unlikely assumption), it entailed instantiating a struct that would be available as memory to each "state", and then doing basically what you describe with function pointers for state transitions. I remember being vaguely aware that I was essentially creating a directed graph that would be used to determine what to run next, but looking back, I don't think I made the final logical step from there to realizing that this was just an implementation of state machines (which I knew about from my more theory-oriented classes); at the time, I remember thinking that it was a rather cumbersome way to specify what code to run next instead of just writing out everything I wanted in order. I hope my TAs were as amused reading what must have been a giant heap of spaghetti code as I am thinking about it now, but I probably wouldn't be amused actually having it in front of me and having to read it along side a few dozen other project submissions that were written similarly.
As long as it doesn't run a foul of reasonable expectation of privacy.