skysight-inc/HackerNews huggingface dataset:
A megacorporation doesn't act like my 85 billion neurons. A corporation acts like a forest of trees, or at best, an anthill. Corporations (and simple organisms) respond to their environment, but not necessarily in incentive-driven ways. Often, corporations move opposite incentives not because of some local minimum or whatever, but because it, for example, personally benefits the CEO, a few board members, or a group of employees.

I can set up "incentives" for an anthill, in the form of a mixture of sugar and borax. Emergent behavior takes over.

The behavior of corporations, at the scale of Google, Facebook, or similar, is almost entirely emergent dynamics. Same thing for countries, for that matter.
The Lisp people absolutely got something up and running quickly, which is why Lisp is one of the earliest languages. Big, institutional Lisp systems were in a different state of maturity when Unix was coming up.

Early Lisp didn't have defmacro with destructuring, backquote, lexical scope, condition handling, structures, hash tables, ... you wouldn't want to use it today.
You should have started speaking Glaswegian. They'd have stopped the lessons instantly.
The terms might be classic (whatever that means) but the meaning varies from place to place and time to time.

Class in the UK does not necessarily have the same meaning as in the US for instance.
I would say secrecy, not dishonesty.
I can't see how you'd interpret this as "advertising a cool hack."

The entire original article:

I initialised a new Git repository, and added a .gitignore file instructing git to ignore .gitignore:

git init .
echo ".gitignore" > .gitignore
git status

And the result:

On branch trunk
No commits yet
nothing to commit (create/copy files and use "git add" to track)

Therefore, we can see Git ignores .gitignore because its in .gitignore, which means it didn’t ignore .gitignore for instructions.

Is any of this informative, surprising, or useful? … Absolutely.
Interesting, I found a feature request for a "play next" on their community forums [0]. They responded:

> We've discussed this feature in-depth internally and also carried out a variety of tests with different groups. Based on the results we can confirm that for the moment we won't be changing the existing way queueing works. As we don't have any immediate plans to implement this, we'll be changing the Idea Status to Case Closed.

Added my +1 and keeping my fingers crossed that they revisit :)

[0] https://community.spotify.com/t5/Closed-Ideas/Queue-Queue-to...
It is bad which is why all of these OSS products have consortiums and millions of marketing dollars behind them. Just look at the Platinum members of the CNCF. All cloud companies for the most part. Who really benefits from Kubernetes? I suspect it's the wallet of the Platinum members...

I'm not saying the technology isn't good or solves a certain problem, but the reality is kubernetes is being heavily marketed and in many cases I've encountered it wasn't a good fit for what the team was trying to do. A server and copying files would have been easier but they've already made an investment and going back would look like failure.
There seem to be quite a few of the originals on YouTube - not sure if we can get automated translations.

The Water Margin really was essential watching at that time. Not sure that the subtleties of script changes would have made much difference to it’s audience though.

PS I also went to elocution lessons but managed to persuade my parents I was a lost cause after two lessons!
Yeah, what I really meant was "pre-prediabetes." Because temporally what's called prediabetes usually occurs after being overweight too. If there is a physiological switch that, once triggered, leads to diabetes and also causes obesity, then it would also explain the odds-ratio but it would not be obesity causing diabetes.
There are many millions of car accidents every year, with less than 1% resulting in death. The most important factor in fatal accidents is the speed at which the crash occurred. In the city, traffic density often prevents fast driving, regardless of speed limit. Less traffic means people can drive faster. This doesn't seem like a mystery to me.
If Godel's theorem applies to all formal systems. Then in formalizing Godel's theorem, doesn't that make the theorem apply to itself?

So the calculus that formalises the theorem is either inconsistent or there are other true statements about it that can't be proven? Which is it? Can someone with a bigger brain elaborate on how the theorem applies to itself in a language for tiny brained people? No big words please.
just set this up on my machine! Thank you so much!

I'd just been bumping into this problem, but hadn't conceptualized such an elegant solution, so kept fumbling around, adding/moving things, futzing around with git way more than I wanted to.

Thank you!
You might have learned the wrong lesson.

A broken code should not be able to make it to production, there should be several steps to prevent that, including: Peer review, CI, QA, a staging environment, manual testing, etc.

Always assume that developers can screw up in trivial ways, and build your delivery system such that trivial screw ups will be caught early, rather then dictate how your devs setup their work stations.

Also don’t code review the code it self, review the diff.
The Erlang 'maybe' expression expands on what 'with' allows in Elixir, mostly because the 'with' construct allows a list of conditional patterns and then a general 'do' block, whereas the Erlang 'maybe' allows mixed types of expressions that can either be conditional patterns or any normal expression weaved in together at the top level.

It is therefore a bit more general than Elixir's 'with', and it would be interesting to see if the improvement could feed back into Elixir as well!

The initial inspiration for the 'maybe' expression was the monadic approach (Ok(T) | Error(T)) return types seen in Haskell and Rust, and the first EEP was closer to these by trying to mandate the usage of 'ok | {ok, T}' matches with implicit unwrapping.

For pragmatic reasons, we then changed the design to be closer to a general pattern matching, which forced the usage of 'else' clauses for safety reasons (which the EEP describes), and led us closer to Elixir's design, which I felt was inherently more risky in the first drafts (and therefore I now feel the Erlang design is riskier as well, albeit while being more idiomatic).

So while I did get inspiration from Elixir, and particularly its usage of the 'else' clause for safety reasons, it would possibly be reductionist to say that "the good ideas were stolen from Elixir." The good ideas were stolen from Elixir, but also from Rust, Haskell, OCaml, and various custom libraries, which have done a lot of interesting work in value-based error handling that shouldn't be papered over.

I still think these type-based approaches represent a significantly positive inspiration that we could ideally move closer to, if it were possible to magically transform existing code to match the stricter, cleaner, more composable patterns that they offer.

In the end I'm hoping the 'maybe' expression still provides significantly nicer experiences in setting up business logic conditions in everyday code for Erlang user, and it is of course impossible to deny that I got some of the form and design caveats from the work done in the Elixir language already :)

Also as a last caveat: I am not a member of the Erlang/OTP team. The design however was completed and refined with their participation (and they drove the final implementation whereas I did the proof of concept with Peer Stritzinger and wrote the initial EEP), but the stance expressed in my post here is mine and not the one of folks at Ericsson.
I'm a little confused - why does the existence of platinum cast gold as negative? Both are "positive" elements, but one may have greater value than the other.

Maybe that's not what you meant though.
Being only 90% backed by cash isn't the problem. A lot of people could afford to lose 10%, if the money was evenly distributed. Tether would still be a scam in that situation, but it wouldn't destroy the crypto ecosystem.

The risk is that there could be a bank run. People panic and drive down the price trying to get rid of their tether. Now crypto as a whole has lost a lot of the liquidity used to buy/sell crypto. This causes a further panic across other crypto assets.
Even data "hoarding" can be a problem for someone if it begins to consume their life. Sure, the physical consequences aren't as severe as hoarding old junk in your house, but it could possibly become a physical and mental problem for someone. Sure sounds like that is not the case for the OP, as it all sounded like a bit of a joke to begin with. But I'm sure you could find someone for whom data hoarding is a real problem that negatively affects their life if they feel compelled to constantly seek out stuff to archive and begin filling their house with storage media.
Have you checked out thin.dev? We provide optimistc updates, local cache and realtime is the default for everything (offline persistence has not been the focus as we're not targeting mobile for now)
A common definition, which happens to better capture my idea of what tether is doing (wrong), is that a bank transforms short-term deposits into long(er)-term loans.
Wonder if they'll block Firefox next since that (like many) allows you to download and install an apk just by opening it
That's why it takes about 3x the effort and money to make a smallish CRUD app than it did 25 years ago. Too many eToys to distract decision-making. Warren Buffett said one of his top "skills" is not being afraid to say "no" to dubious investments and ideas. Nobody is saying "no" to our bloated web stacks. When I complain about bloat, I'm often given the reply, "but look at all the wonderful things you can potentially do in the future!" YAGNI, KISS, and DRY have been shot bloody dead.
Coinbase isn't paying $380k base either..are you just quibbling over the meaning of salary?
This is a really bad analogy. And mining has many, many harmful impacts on the environment over typical consumer product usage.
>I mean in private conversation, not in public discourse, and this is not to their faces but rather behind their back.

0 or never. Even if it were to their face.

You will never achieve your goal using criticism of individuals.

This is even true of celebrities or public discourse. You have to hit an exceptional threshold before you can even criticize celebrities.

Take Jordan Peterson's recent rule breaking. He needlessly criticized: https://twitter.com/jordanbpeterson/status/15262791815453900...

He was even punching down here. In fact the only legitimate criticism here is against JP. He certainly meets the threshold where he has gone too far and should be apologizing. If he doesn't we should be criticizing.

6. "Set your house in perfect order before you criticize the world."

That's his own damned rule and he's clearly violating it. His sorry not sorry is that he blamed the toxicity of twitter. He's still in the wrong and we should criticize him.
> It's constantly trying to play albums in random order, and even more egregiously, related tracks when the current album finishes.

(The following may vary in some details between desktop and mobile versions of Spotify, but the general idea works in both).

On my iPad it only shuffles playlists by default, not albums. To play a playlist without it being shuffled the trick is to start it by clicking the first song rather than clicking the playlist's play button.

Clicking the first song starts that song playing and sets the "next from" list to the rest of the playlist not shuffled.

Starting an album by clicking the first song instead of hitting the album's play button works the same way, so simplest is to always start both albums and playlists that way unless you actually want shuffle.

The above works if what you want to do is listen to a specific album or playlist and then when it is finished choose another album or playlist, assuming you start with a clear queue.

If there is anything in the queue it will play the song you clicked, then the queued items, then the rest of the "next from" list so clear the queue either before you start your album or playlist or before the first song finishes.

If what you want to do is listing to more than one album or playlist in a row, without shuffling, and without having to wait until one ends to choose the next, you might think you could start the first one using the above method, and then while that is playing add the others to the queue but that fails. The queue has priority over the "next from" list.

The best way I've found to play multiple preselected albums is to simply make a playlist for this and add the albums to it in the order I want to hear them, and then play that playlist as described above. Next time I want to listen to a different set of albums I delete the previous play list and remake it with the new albums.

I'm not sure how to play multiple preselected playlists in order. You don't seem to be able to copy a playlist to another playlist, so the trick for multiple albums does not work. You can queue the playlists one after the other which mostly works, except that if there is anything in the "next from" list that will be played after the last song from the queue.

I don't know how to clear the "next from" list, but here is a hack. Make a playlist with a single song. Start that playlist and then hit pause. Now add your other playlists to the queue, and then hit the "next song" button to start the queue. When the queue finishes that song from the one song playlist will become the next up song but it won't start playing because it already played.
Yea I agree about MagSafe. I thought that made sense to have and was a very nice feature. I always hated the HDMI/USB-A/SD ports because you never knew what you'd run into and you'd wind up having to carry or look around for adapters and all that. Would have been nice to just transition to straight USB-C everything. Yes that would have taken time, but I strongly believe it would have been an improvement.

I agree that Lightning is actually not a bad little port at all, but I'd sacrifice that to just have USB-C to USB-C everywhere and not have to have more than one cord.
London != Europe
Ah! I remember reading something about self-optimizing interpreters, which is pretty cool. I think it's related to what they call "adaptive interpreter".

The interpreter starts out with a generic/slow approach and as it gets more datatype info it uses more specialized and faster implementations.
I would say things have changed noticeably just in the last 2 weeks (in terms of recruiter engagement, news about funding rounds, news about hiring freezes). If you started interviewing in early April it's a lot different than now.
Or worse, doing a little farce where they supposedly "choose their own".
Netflix treats employment as a contract, they will pay you a lot and are very clear that the contract may end at any time. This is how adults should act. There’s minimal emotional manipulation which is almost never the case with corporate culture. Corporations generally try to get you to act against your best interest for the “sake of the company”.

This type of high-pay contract-style work is extremely common in industrial construction. You’ll get paid $500k+ / year when you get attached to a project, and you are unemployed when that project ends until the company gets another project. It’s referred to as “breathe in, breathe out” and people genuinely enjoy it. High pay when there is work, and lots of free time between projects.
I really like what I've read about Kagi, and I'll likely end-up paying for it too, but I _hate_ the metered fee.

I've never run a search engine, but I don't imagine that offering "Unlimited" searches where "unlimited" means "do not abuse" would meaningfully hurt their margins. As a benefit, you avoid losing customers that then need to ask "Do I make more than 5*80 searches a month? How many is that a day? What do I if I go over?". It also just feels like I'm being nickle-and-dimed.

I love that they're charging for the service, it makes me feel like they're building something sustainable. I just don't love the fee structure.
Last Big Mac: Russians line up ahead of McDonald’s exit
Disagree. How is that a bad habit? My workflow is "git status" to check what I've changed, "git add --all" and then "git commit".

"git status" needs to be clean. I don't want to see any untracked temporary files. If it's untracked either it needs to be ignored or it's a new source file to add to the index.

Keeping untracked files lying around not gitignored is a recipe for one day committing one by mistake, or conversely, that some of them are source files you've forgot to commit. I've seen both things from junior developers, that do not know of .gitignore.
I second your discomfiture at gray text.
> Allow WAL full page writes to use LZ4 and Zstandard compression

This would affect streaming replication, which is basically WAL shipping, I presume?

Most of the interesting stuff to me that I'm seeing this release are around not streaming, but instead logical replication:

> Allow [ed: logical replicataion] publication of all tables in a schema

> Allow publication content to be filtered using a WHERE clause

> Allow publications to be restricted to specific columns

> Add two-phase information to the logical replication stream

A lot of neat tools for replication, which will all help a lot of the interesting Change-Data-Capture work that's been emerging. Getting on my high horse here: making the database not just a store of data to be queried, but a source of truth that others can subscribe to, adding reactivity to our core data systems, is a big ongoing & interesting work of the decades. A sizable part of what made etcd so popular, I tend to think, is it's somewhat easy to use Watch API[1]. Seems like there's a lot of new tools happening in 15 for this.

Some other random selections:

> Allow SELECT DISTINCT to be parallelized

> Add SQL/JSON-standard JSON constructors. Add SQL/JSON query functions JSON_EXISTS(), JSON_QUERY(), and JSON_VALUE(). Add JSON_TABLE function to cause JSON data to be treated as a table.

[1] https://etcd.io/docs/v3.2/learning/api/#watch-api
Dutch companies pledge to not avoid taxes
Yes, It detects foreign key based relationships automatically.
QT has retreated to what is the absolute minimum it has legally to do. They can't pull away any more. QT and KDE have legally binding agreement.

>All software changes in Qt will still be available at as Open Source as
required by our contract – maybe with a delay of 12 months if the company
decides to part ways with the communities.

It's hassle to maintain LPGL version with 12 month lag for sure.
Noisetorch Possibly Compromised
trying to get this out to people ASAP. I have reason to believe at least one of my systems is compromised. Official binaries may not be safe.
Unfortunately not, it isn't. Tried to do it when migrating from Google to Mailfence, but gave up since it missed some messages, randomly timed out and couldn't continue.

In the end I had to remove all messages, and process them using Claws client, which gives much better control and a feedback which messages were transferred and which failed. The only issue I had is that some messages were transferred multiple times, but Claws even has a solution for that by using "delete duplicate messages".
This is one of the reasons I'm focused on helping self-hosting take off. It reduces the complexity of the software by an order of magnitude, while retaining much of the scalability.

One problem is it's still too hard. Hosting your own Gitea/gogs shouldn't be any more difficult or less secure than installing an app on your phone. This is where my work is currently.

Another problem is things like repo stars. You can federate, but then every instance has to deal with spam. Not sure what a great solution to this is.
Yes, Biden is owned by incumbent corporate interest. Any change will have to be despite them.
Firefox has "Reading mode" button right in URL box. Both on desktop and mobile. Enjoy!
Supabase developer here. We concentrate on the following core features:

Database (PostgreSQL with Postgrest for REST)

Auth (GoTrue)

Storage (S3, or local files if self-hosting)

Edge Functions (Deno, deployed across dozens of regions)

Realtime (a lot of new stuff coming up in this space now at Supabase)
It could be, but in this instance it was not. It was an internal application that Gitlab had control over making an internal idempotent request.

The underlying root cause should be identified so that this same issue can be corrected when retries aren't a solution, but if this was causing Gitlab Pages to burn through it's SLO (which is stated in the article), the Pages team could have (and should have) stopped the leak with a retry which the root cause was being determined.
What about people that cannot physically interact with their monitor (MS, missing hands, Parkinson)?

What about people using someone else's computer and hence having no control about changing such settings (public computer, pair programming)?

It makes sense to make stuff accessible by default.
Out of curiosty, could anyone explain to me the reason they think programming languages and the parts that combine into making them work are interesting?

I feel like I have an interest in it, but I'm having a hard time figuring out _why_ I find it so appealing.
I know the why doesn't matter as long as I enjoy it, but I'm curious what others think.
The liability protection in Section 230 relates to user generated content. CNN formerly allowed such content on their web site in the form of user comments on news stories, but they removed that feature in about 2014 because it wasn't profitable.

Which specific case law are you referring to? Please provide an actual citation because I don't think anything in my comment contradicted an opinion by Judge Orrick.
> All of them set a hierarchical pyramid of OKRs that cascaded down, rather than a set of OKRs that worked bottom-up, even if the company wasn’t in a crisis and would have benefited from promoting innovation.

Maybe I've only worked companies that do OKRs wrong, but I can't imagine what the bottom-up version of this would even look like. Individual teams pick their own OKRs, and then the exec above that looks at all of the OKRs that their various teams have decided on and then summarizes them in some way as their own OKRs after the fact?
I think every person entertains many ideas. Being receptive to possibilities does not define you, but it may incline you. 'Criticism' can play a valuable role in helping you see demerits in your inclinations before you misbehave.
That's good. I didn't come to the BEAM ecosystem from Ruby, so I prefer Erlang's syntax to Elixir's.
Devoted to the unused parking! 2/3s of that drive thru line could be parked with their engine off.
Pretty much what I was about to say. Instead of finding ways to make something mostly out of your control (i.e. work) interesting, it's better to do less of it and use your free time for interesting projects.

The key, of course, is to get a job that isn't as demanding. Personally, I've found that most of those jobs don't pay more nor have better career growth anyway.
The last I looked Calibre, including its CLI tool ebook-convert, is literally the only local option, paid or free, for consumers to convert EPUB to AZW3. If you know of anything else please let me know.
EU plans ‘massive’ increase in green energy to help end reliance on Russia
I'm not sure what point you're trying to make, clearly enough people do pay for commercial software to fund it's development, otherwise it wouldn't get funded. Therefore, as a matter of gob-smackingly obvious reality, it is affordable enough for the model to work. I feel bad for Peruvians that can't afford it, I hope they find a way to get by, but that doesn't make the existence of commercial software a bad thing.
They are likely removing IMAP. IMAP support is already disabled by default in Gmail