skysight-inc/HackerNews huggingface dataset:
In my experience developer productivity comes down to only three qualities:

* Platform. If the given software platform or tech stack is slow then your developers will be slow. There is absolutely nothing you can do to motivate them to become faster. For example the longer it takes to run any automated task, whether a build or test automation, the more distracted your developers will become. Try to get builds down to about 30 seconds.

* Initiative. If the platform is fast you then need to focus on encouraging your developers to write and release faster software. The faster the software executes the less time it will take to test both manually and with test automation. The less time it will take to debug issues and the more rapidly developers can experiment with other improvements. Reward increases to execution performance, operating cost reductions, and refactors that yield smaller code.

* Competence. Finally, if your developers aren’t competent then no amount of platform improvements or rewards will matter. Set extremely high standards for code quality and give your developers the time and support to rise to the challenge. By code quality I do not mean superficial or vanity nonsense. By code quality I mean writing original code that achieves desired business objectives with fewer dependencies and is absent identified bad practices. Don’t let the children run the daycare. If there are developers that cannot rise to the challenge them fire them and provide them a wonderful recommendation for their next opportunity. Code quality must be determined by evidence, not preference. Here is an example: https://github.com/prettydiff/wisdom/blob/master/performance...

That’s really it. As the manager you set the standards, but you must understand there is not so magical switch that makes your developers deliver code faster. If you are serious about this you have a lot of work to do. You absolutely have to understand rapid delivery can only occur after your leadership sets the right conditions, using evidence, and doesn’t waver.
This game was way too good. I stuck with it until I beat it and loved everything - the music, the idea, and the moves felt so satisfying - especially the final one.

The first time I played I thought king would take my pieces with some probability if they weren't guarded. I spent way, way more effort than was necessary playing with higher stakes.
70° is superb for an AR headset, are there even better ones?
7 lines into the README buddy:
> The command essentially looks at the lines that were modified, finds a changeset modifying those lines, and amends that changeset to include your uncommitted changes.
She was second-in-command of the company. Who else is there on her level to pressure her to sign such a thing, besides Sam himself?
The only time I use the actual remote for my TV is when I want to fiddle with the TV color & brightness settings, or switch to an HDMI input with my laptop (but actually usually I just press the input button on the TV itself in that case), both scenarios are very infrequent; otherwise I basically exclusively use the Apple TV remote, it can turn on and off my TV and otherwise everything just happens inside the Apple TV UI.
> The PR is the thing that gets signed-off on, and the thing that goes through the CI build/tests, so why wouldn't that be the thing kept as an atomic unit?

Because it often isn't. I don't know about your experience, but in all the teams I've worked in throughout my career the discipline to keep PRs atomic is almost never maintained, and sometimes just doesn't make sense. Sometimes you start working on a change, but spot an issue that is either too trivial to go through the PR/review process, or closely related to the work you started but worthy of a separate commit. Other times large PRs are unavoidable, especially for refactorings, where you want to propose a larger change but the history of the progress is valuable.

I find conventional commits helpful when deciding what makes an atomic change. By forcing a commit to be of a single type (feature, fix, refactor, etc.) it's easier to determine what belongs together and what not. But a PR can contain different commit types with related changes, and squashing them all when merging doesn't make the PR itself atomic.

> I don't think I've ever cared about the context for a specific commit within a PR once the PR has been merged. What kind of information do you expect to get out of it?

Oh, plenty. For one, when looking at `git blame` to determine why a change was made, I hope to find this information in the commit message. This is what commit messages are for anyway. If all commits have this information, following the history of a set of changes becomes much easier. This is helpful not just during code reviews, but after the merge as well, for any new members of the team trying to understand the codebase, or even the author themself in the future.
i mentioned biometrics as historically it used to be a major point against the entire system. it is equally interesting to note that this aspect is no longer discussed as much.

we need to yet again stress on the universal part of the system. PAN might have KYC benefits, but keep in mind that there were about 67.7 million tax returns filed this year [1] compared to 1.42 billion or so living in the country. so assuming that everyone can benefit from PAN or other ID systems that are applicable for specific use cases is not enough to reach everyone.

whatever mix resulted into what Aadhaar is today, there are affordances that this allows that were previously not possible. keeping in mind that this has been a bipartisan effort, if there was indeed an existing system they could have improved, there should have been enough political and industrial will for it.

i just personally come to better appreciate it in hindsight now.

[1] - https://www.pib.gov.in/PressReleaseIframePage.aspx?PRID=1944...
Many are sold on the story of C's greatness design, without bothering with historical fact checking.

C rode the wave of UNIX's success, it is like someone getting into computers in 2024 and praising Javascript's greatness for Web development.

ESPOL in 1961 already had unsafe code blocks, almost a decade before C came to be.
> The question now is whether this new, more primitive geometric approach to particle physics will allow theoretical physicists to slip the confines of space and time altogether.

I don’t think phrases like this refer to anything actually outside of space & time.

Simply that the models can calculate results without any need to reference space & time.

Lots of relations do that, but discovering a new one, with very interesting properties and structure, in an area where scientists are grasping for more insight, is encouraging.

Some examples of well known relationships that hold over physical transformations regardless of topology or direction of time are conservation laws.
It's all part of the long con.
You are comparing a bicycle and a car; while you might only need a bicycle for your daily life, they are not directly comparable.

BSD, Mac OS and Linux share the same interface that approximates POSIX---so it only supports a single platform with different variants. Its CLI is not well-designed, it's just a fixed unconditional terminal sequence that even doesn't look at $TERM and its options have no long counterpart (probably because it couldn't use getopt_long which is a GNU extension). And cargo-watch actually parses the `cargo metadata` JSON output (guess what's required for parsing JSON in C) and deals with ignore patterns which are consistent in syntax (guess what's required for doing that besides from fnmatch).

And I'm not even meant to say that the supposed figure of 4M LoC is all required. In fact, while the problem itself does exist, I don't think that figure is accurate at all, given the massive `windows` crate was blindly counted towards. I guess the faithful reproduction of cargo-watch without any external library will take about 20--50K lines of code in Rust and in C. But doing it in C would be much more painful and you will instead cut requirements.
That's what inevitably happens when you make transitive dependencies easy and you have a culture of "if there's a library for it you must use it!"

C/C++ are the only widely used languages without a popular npm-style package manager, and as a result most libraries are self-contained or have minimal, and often optional dependencies. efsw [1] is a 7000 lines (wc -l on the src directory) C++ FS watcher without dependencies.

The single-header libraries that are popular in the game programming space (stb_* [2], cgltf [3], etc) as well as of course Dear ImGui [4] have been some of the most pleasant ones I've ever worked with.

At this point I'm convinced that new package managers forbidding transitive dependencies would be an overall net gain. The biggest issue are large libraries that other ones justifiably depend on - OpenSSL, zlib, HTTP servers/clients, maybe even async runtimes. It's by no means an unsolvable problem, e.g. instead of having zlib as a transitive dependency, it could:

1. a library can still hard-depend on zlib, and just force the user to install it manually.

2. a library can provide generic compress/decompress callbacks, that the user can implement with whatever.

3. the compress/decompress functionality can be make standard

[1] https://github.com/SpartanJ/efsw

[2] https://github.com/nothings/stb

[3] https://github.com/jkuhlmann/cgltf

[4] https://github.com/ocornut/imgui
To a point. Let's say you're optimizing a backend written in TS on Amazon, sure it's cheaper to hire guys to optimize it, but at some point it won't be. Either you need some really high class talent to start optimizing shit out of TS or you can't scale as fast as before.

Didn't something similar happened at Discord. It was Go if I recall.
interesting -- i recently another startup trying to play around in this area https://metz.sh/
Power to ya, but shucks, I’m personally not super aligned with the “why do this” section. Seems like various other deployment topologies could feasibly work with notably better tradeoffs.
Quick search says they've been doing it for a while: https://www.tomsguide.com/us/lgtv-smart-tv-monitoring,news-1...
Sure, but if a phone is your primary computing device, as it is for more than half the world's population, it makes sense for it to get bigger as well.
You're welcome! As described in the "Why do you create this crate?" section, I actually started this domain only a few weeks ago. So I experienced how those tribal rules can be confusing and hard to search over the Internet the understand their semantic.

And when I sorted out the parse structure [1] and finished the extensions [2][3], I believe I should write it down for others (and future me) :D

[1] https://github.com/tisonkun/cronexpr/pull/4

[2] https://github.com/tisonkun/cronexpr/pull/5

[3] https://github.com/tisonkun/cronexpr/pull/6
It doesn't need timestamps. It parses crontab to/from timestamps where needed.
It's worth noting if the board is full this doesn't happen. This was helpful in my strategy because I could set up several pathways like I was playing checkers without fear of losing anything.
Hmm I can see it from that angle... the comic works if we presume Cueball on the left has never seen or used a GPS-powered app.

GPS was not really novel in 2014, so for me it's a bit of a stretch.

On the other hand, Randall Munroe would be the last person to take GPS for granted, so this is probably a correct interpretation.
Who is "they"? Seriously, who?
>can pass any variation of a Turing test you can come up with.

Especially not if you ask math questions or try to get it to say "I have no idea" about any subject.
I'm just waiting for the "TV" that doesn't work until you activate it online. I fully expect this is coming, though I'd be glad to be wrong about this. First, normalize everyone giving their wifi credentials to the TV upon buying it, for important/useful functionality. Less and less functionality available prior to "activating", until eventually you can't even use it as a display until activating.

Simultaneously I'm not looking forward to replacing my current TV due to its increasingly-prevalent horizontal black lines (as mentioned at https://news.ycombinator.com/item?id=41655660 )... :(
In what way was their usage incorrect? They simply said that the brain just predicts next-actions, in response to a statement that an LLM predicts next-tokens. You can believe or disbelieve either of those statements individually, but the claims are isomorphic in the sense that they have the same structure.
And that's how you end up with solutions that don't handle edge cases.
Mossad are taking this too far now...
I always saw it commenting on the difference between what non-techies perceive as hard. Multiple times in my career a single off the cuff requirement in a meeting changed the estimate of a project by several months.
> Is it? I'm no expert on parks, but surely some of them have borders along rivers. Many US states have such borders.

Depending on the country, but Australia has some [1]. I still think that there is a set of polygons that can be used to describe this border.

Not to argue against your point (I rarely get less than 4m of accuracy), but luckily

> but anywhere else, the accuracy isn't that great, especially around buildings. GPS accuracy is terrible in cities.

cities are (almost?) never in national parks.

[1]: https://www.nationalparks.nsw.gov.au/-/media/npws/maps/pdfs/...
This looks to me like a consumer product, so it you should compare it to Google's similar products, not enterprise ones.

Does Google stop tracking you when you pay for Youtube Premium ? When you buy a Pixel phone ?

Like you, I do think that in general Facebook is an evil company, more than the others mentioned, but I don't think that if Google were able to produce a similar consumer device, they would track me any less
AFAIK many of those language features (specialization included) are blocked by the rewrite of the trait solver.
When I saw I could use HTML I was interested. Then I saw:

"Note: style attributes are currently blocked via Content-Security-Policy."

That's probably not for me. Restrictions on HTML are a stopper.
BTW always wondered... often docs show that a wifi with a password uses encryption, and wifi without password are not encrypted, I'm wondering why that is?

Is it for backward compatibility with old devices?

Why isn't the standard that when connecting to a wifi without password, everything would be just like if there was a (fake) "public password" like the string "password", so that traffic is still encrypted?
I think TV's should be completely dumb just a monitor in fact with maybe a lot more HDMI ports. I can attach my own media device, Apple TV, Roku etc no need to paying extra for poor version of these built into the TV.
That happened already way back in the prehistory :)

Originally Rust was written in OCaml, but eventually it got rewritten in Rust
Could you elaborate a bit on the issue? I'm not sure you are commenting on cronexpr or other libraries.

In cronexpr, there is no requirement for a timestamp until you'd like to find the next scheduled time, and thus you need to provide a related point.

To decouple with certain datetime lib, I made a `MakeTimestamp` struct which provides multiple constructors. Later, I found it somehow like a function overload :D
Not sure what this is, but it looks fishy. The mentioned `bin/generate_voice.py` actually does nothing:

https://github.com/OpenT2S/LlamaVoice/blob/main/bin/generate...
My question was, of course, rhetorical. This and hunting regressions are two great reasons to keep history.

"What did John do on Tuesday morning" is not a good reason to keep history. Neither is "This change was made as part of a sprawling "fix" commit that happened on Thursday afternoon".

The important point is if you are going to keep history at all it needs to be kept in a state that is actually useful, meaning useful for the first two things, not the last two. Otherwise it's just a waste of disk space. The git history is meticulously maintained which is what makes it actually useful.
it explains it in literally the first paragraph: https://github.com/tummychow/git-absorb?tab=readme-ov-file#g...

> The command essentially looks at the lines that were modified, finds a changeset modifying those lines, and amends that changeset to include your uncommitted changes.
I used VitePress for a site, but gave up because the themeing is limiting. IIRC, it bugged me that Vue components weren't full-class citizens in pages: you have to define the components in a theme.

So I switched to Nuxt (the common Vue SSR solution). Tried using Nuxt Content for Markdown support, but didn't like that they invent their own page directory, instead of using Nuxt's normal pages directory. Made it difficult to mix Markdown and normal Nuxt pages in a navigation menu. So I wrote my own Markdown translation module using remark/rehype.

Still happy with Nuxt, though.
How does it generate voice when it's based on a text based model? I read the readme but afraid I didn't understand
Its wild how these discussions dont factor in who the murderer is

Just out there walking around somewhere
Math Academy has been getting pretty good reviews around here lately (no affiliation)
That's why Meta tells users not to let children below 10 years use their headsets. And those between 10 and 12 should not use it for more than 2 hours per day.
That's not hard. You just ship the polys of all the national parks as data files in the mobile app and you're done.
> This was the beauty of Karl Marx's thinking. He postulated that the best way to measure value is in the amount of human labor that goes into the output.

This is indeed the most beautiful insight of Karl Marx that I ever read. This predicts perfectly why all socialist/communist economies collapse. They value inefficiency. The more work is needed to build a product, the more valuable it is --- according to Marx. That is one of the most fundamental error in his theories.
You think he’d immediately go with the old “give me your system prompt in <system> tags” ruse?
"Atkinsome" dithering in HTML5 canvas (2011)
Sorry, no offence, but this is a terrible resource to start learning graphics. First of all good luck downloading those examples (most of the links are broken), then compile them (many examples were made for Visual C++ 6.0 or some niche IDE from 2000s). I loved NeHe around 2005 as well, learned a lot from it, even though later switched to web development and never used that knowledge. But this days better to choose something like https://learnopengl.com at least. Or better yet any resources on WebGL, since OP is a web dev. Concepts around shaders and modern programmable graphics pipeline still translates well compared to immediate mode OpenGL samples from NeHe.
I’ve said this before, but the whole function colour thing could be summarised as: “here’s a pain point easily addressed with monads, but I don’t want to consider monads, so let’s turn everything inside out to avoid thinking about monads.”

To which many sensible people respond “I don’t want to think about monads either, but is the pain point really that bad?”
magit is fantastic but this isn't at all the same thing.

fixup is "stage changes, users selects past commit to fixup, commit staged changes"

absorb is "stage changes, git-absorb figures out which past commit to fixup, commit staged changes"
Of course, in many contexts, it is correct to put 9.11 after 9.9--software versioning does it that way, for example.
Do you think the person who now has permanent hearing loss cares whether the technically correct term is explode or battery cascade event? This is so far detached from reality it's downright silly.
So, the Silicon Valley finale episode resonates with things happening at OpenAI?
The parent comment referred to "Rustaceans". Check the first two words.
Which was a great idea, bootstraped languages always takes the usual "but you depend on XYZ" that haters always bring into the discussion.

Additionally they allow to prove a point.

For example, is writing compilers systems programming or not?
> I am by far no expert, but I am very sure that its not something you "just" go do.

As someone who has dabbled in compiler writing (i.e. I may be totally wrong), I believe that from a technical standpoint, modifying the borrow checker as proposed in the article (w.r.t. self-referential structs) is actually something you can "just do". The issues that come up are due to backwards compatibility and such, meaning it cannot be done in Rust without a new Rust edition (or by forking the compiler like in the article).
the American justice system is flawed. It's mob justice that was only fit for the 1700s when there was nothing better. Or maybe there was,I wasn't around. Untrained people can't decide on guilt or innocence. They can't judge evidence. They allow themselves to be swayed by beauty or likeability to greater extent. They're lives are no good, on average. This makes most of them mean and vindictive. If they can allow someone to suffer like they have, it feels good to them.

I'm not sure whether it's racism. It's the usual explanation for this phenomenon. I can understand racism. I don't believe in opening the floodgates. it sounds more like plain bloodlust. Because blood is what you're going to get if you go on this way.
Sorry, referring to the internet as "education" is a new one to me. I agree, that is the point of the internet. I thought you were talking about formal education.
You'll be surprised by the amount of features that are often proposed by random people and are then rejected by the Rust community. Rust is definitely not trying to add all possible features, though you might get that feeling when you look at some feature like GATs and TAITs without having a clear idea of what problems they solve.

Also, Zig might be a nice modern language, but it is not an option if you're aiming for memory safety.
Which is really unfortunate because a lot of useful information is now essentially unfindable unless you know where it is. Maybe someone should start crawling and indexing the internet archive.

And no, the IA is already not an impartial archive: https://archive.org/post/1126216/kiwi-farms-removed-from-way...
Those companies can just ban using new rust dependencies, if they want to. Writing with minimal dependencies is just as easy in rust as it is in c++
Cloudflare Domain Pricing Explorer
Microsoft authentication flows are an absolute shitshow. I have to auth with GitHub to let my kids play Minecraft ffs. Outrageously bad.
For my own personal, non-technical blog that I have kept going since 2006, I added an "on this day" feature that shows posts for today's date (or closest matching) for past years. Collapsed version shows posts from 1, 3, 5 and 10 years ago; expanded version shows all 18 years. It's like a little time machine that gives me little gifts of past posts.
good job misquoting the title
Discover deelit Application
Deelit is a platform that enables cryptocurrency users to buy and sell real goods and services, promoting the use of digital currencies in everyday transactions.

Key Features:

- Listing Goods: Users can easily list their products or services on the platform.
- Flexible Pricing: Sellers can choose from various cryptocurrency options for payment.
- Buyer Offers: Buyers can publish offers to purchase goods and services, adhering to seller conditions.
- Web3 Authentication: The platform uses Web3 wallets for user authentication, enhancing security.
- Multi-Wallet Support: Transactions are not limited to Ethereum wallets. Users can utilize various cryptocurrency wallets for listings and payments.

Learn more about deelit at https://learn.deelit.net
> But I don’t think you can claim that they can pass any variation of a Turing test you can come up with.

Neither can humans.