skysight-inc/HackerNews huggingface dataset:
I've built a few open source things in the past, a couple of which got popular. One was an open data project and it's just stayed the same (free API etc). Community look after it mostly.

Another was what became Certify The Web, which is now the most popular UI for automated certificate management on Windows and is most definitely now a commercial product (but 90% of users use the free version). I originally had a donate button and did get a couple of donations, maybe 4 or 5.

It was getting thousands of downloads per week and the company I was working for went into administration, so on the same day I added a Paypal button to the website for people to buy a license key and got my first sale later that evening. It's now had around 10K customers over 7 years and they renew their license key each year. Some people/companies do indeed want support and updates (I offer email support only, or there is a community forum). Nowadays most purchase via Stripe,
My heart's in the highlands is just beautiful, can't stop listening to it
It's simple: understand what the goals of your team are for the current year. Write the code with supporting those goals in mind.
> In the future people might think the same about Bitcoin and AI.

Perhaps, but these will be different people than those who miss the 90-00 internet.
They're also violating the ePrivacy directive with any consent dialogs that don't give at least equal weight to the "Reject all possible and continue" option or hide it behind extra clicks.

Sadly the ePrivacy implementations were a bit lacking in some member states and the EU directive to replace them with a direct EU-wide law doesn't seem to be fully in effect just yet but I have high hopes we'll see companies fined over these deliberate misdirections soon and that will hopefully put an end to it.
The money might not vanish, but you're still working Monday through Wednesday for the government in France. It's as though the government was partly the business owner. The question this raises is whether the benefit for society in the long-term is actually worth it. The larger the share the government takes the less motivated people will be to make things better themselves.
Yes my only exposure to YAML is for Symfony configuration and it's way better than JSON for this.
That lists the pay discrepancy but doesn't mention if there are literally any factors for the disparity such as role, responsibilities, performance, etc. It just mentions race, which gives me absolutely no usable information to give credibility.

If we are to assume black and women workers have historically been missing entirely from tech then the efforts of recent initiatives would bring fresh people in? Those newer people wouldn't have the same length of professional experience but the expectation is to be paid equal?

Put another way if the CEO is white and they make 50m and you have two employees, one black and one white who each make 50k, the average for white workers would be skewed higher? Before anyone replies "um actually, it's only workers within the guild, the CEO isn't included", okay, but does everyone in the guild have the same job title, experience, and responsibilities?

As an aside, they've structured that website like trash. Yes, I'd love to click a link to see the pay study which is just duplicated below the link without any additional information. It's like they purposely are trying to say nothing but be loud.
do you often write stuff and then not touch it for three years?
It is very much a Hideo Kojima game, so answering that question well would be pretty difficult for most folks. Regardless, it’s quite the experience, that’s for sure.
Front end is tricky, but is less security critical as you should not trust the client anyway.

I think Node may be a lot worse than this, but looking at two Django projects, one on which I have really kept dependencies to a minimum and one I feel has two many dependencies I get 9 and 74 dependencies respectively.
>I don’t remember US trying to re-establish its long gone failed empire that collapsed under its own weight.

No, it was trying to maintain an empire of sorts.

>“The only”

What difference do you see in the justification for these wars?

>Just as bad? Don’t be ridiculous, Jesus.

I'm not. It's just as bad. I'm not talking about war crimes; if you had bothered to read more carefully, you'd see I was talking about justifications for the wars, not how the wars were actually conducted once underway. Of course, the US did far better.

>For an outside viewer, first one looks far more plausible than the second one.

How so? Any fool could see at the time that there were no WMD, that the US was rushing to a war on flimsy evidence, and the whole idea that Saddam was in league with Al Qaeda was simply made up, when all the hijackers were actually from Saudi Arabia. I could see it was all BS at the time, and I was just someone watching the news.

>No, US wasn’t the worst in 2000s.

I'm pretty sure the US invasion of Iraq resulted in more civilian deaths than Russia's actions in the 2000s.

And how is the Kursk incident evidence of some kind of evil? It was incompetence and stupidity, sure, but it was an accident: it's not like Russia's government wanted a disaster on their own submarine. What a bizarre comment.
It's likely not even going to be a conscious or intentional choice. At some point your enterprise customers are going to have enough bugs and feature requests to keep you busy full time, and your open source project might languish unless you make a conscious effort to dedicate a percentage of your time on it.

Ironically as some companies have already started noticing, when you stop being able to market your product as open source the start of the funnel will start to dry up. The start of the funnel is often not monitored, and the sales might even continue going up as your successful open source users go to enterprise. By the time you realise the funnel has dried up it might already be too late to turn back as competitors have filled the void you left.
> There is still the issue of the proper interpreter actually being installed, however.

Yeah, that's what I mean with "make it easy". The script header should announce requirements (like what language and language version it is written in, and the shell should be able to ensure those requirements before running the script - without ignoring security aspects of course). E.g. every script should be able to bootstrap itself, no matter what programming language is used (and that might even include compiled languages).
How to Handle International Sales Tax/Vat for SaaS
That is false, you only consent by your explicit action - clicking "accept". If you inspect element and remove the consent popup entirely, you have not consented.
Historically, Cygnus Solutions was very successful at this with custom development on the GNU toolchain.

https://en.wikipedia.org/wiki/Cygnus_Solutions

I don't know if there's something specific about compilers that makes this model work especially well. They would get paid to add specific features to the toolchain that customers wanted, and also to help the customers fix bugs or understand how to do what they wanted.
If someone does not read the terms to a service and then uploaded your private information to that service, and then the service does exactly what they said that they would do with that information, how is that the fault of the service?

My parents raised me to be responsible for my actions and understand their consequences, maybe this is an unusual position?
Please read these original publications instead, it's less clickbait:

https://www.businessinsider.com/tesla-autopilot-fsd-labeling...

https://www.businessinsider.com/tesla-autopilot-data-annotat...

About ignoring road rules:
"Workers can run into data from any number of countries in a single workflow, meaning they must constantly be aware of the different road rules for each region. At times, Tesla seemed to take a more relaxed stance on those rules, seven former and current workers said. For example, some workers said they were told to ignore "No Turn on Red" or "No U-Turn" signs, meaning they would not train the system to adhere to those signs."
it’s already my favourite - great tip
Their monetisation strategy is from cloud hosting and being a data provider, very different from open core.
The document you are referencing has no mention of remote access to a phone. The fact that apple chooses to gatekeep unrelated features and seemingly cites EU regulation to explain this behavior is just absurd. And the amount of people coming to their defense is equally absurd. Have you even understood my main gripe? If Apple feels it is unable to comply with EU regulations with apple intelligence, I can understand that given the amount of raw data that is required to deliver the current generation of AI products. But to then turn around and cite the same regulation when it comes to features that are completely unrelated to data gobbling is mindblowingly stupid, and to me, definitely feels like a tactic to gaslight the consumers in the EU, to try and turn them against this legislation.
This will almost certainly include traditional lands seized or acquired by "paperwork theft" from multi generational family ownership (with no deeds in the western sense). That and land "acquired" by colonial settlement during the past century by equally dubious means.

eg: https://africasacountry.com/2018/12/the-battles-over-land-in...

and: https://www.reuters.com/world/africa/namibian-communities-de...

Fighting the good fight on behalf of benevolant Chinese overlords will no doubt be USofA PMC's (private military contractors) such as Betsy DeVos's brother Erik Prince's Frontier Services Group (or however he's burying his ownerships and interests these days).

https://en.wikipedia.org/wiki/Frontier_Services_Group

I have no position here other than recognising that such shady machinations are commonplace and under the carpet in 21st century neo colonialism.
This comes up every time gdpr or ads are discussed. But it’s pretty simple I think: not enforcing privacy regulations forces site owners to break them.

The reason is that so long as some sites show tracking ads, the monetization possible by privacy-friendly ads is almost nothing.

The long term goal must be that no one cheats, so that ad the revenue from well-behaving advertising can go up.

Remember the consent dialogs aren’t ever asking permission to show ads.
By doing this, you break commit atomicity and make bisects hell. Please don’t do this. Commits aren’t perfect at first for sure, but they should be by the time you make them reviewable.
They dropped it, but the damage to the brand cannot even be quantified. It is fully deserved though and they also stick to their on-demand features.

Not really a car I would ever want to buy if they do not clean up management after such a farce.

This is beyond not being a cool brand anymore.
> So this article is talking about YAML 1.1, while the other article is talking about YAML 1.2.

Precisely. The article is really noticing quirks and limitations libyaml, the library doing the heavy lifting behind PyYAML, not YAML-the-spec proper.

Granted, in practice, library limitations are probably what you want to know about. AFAIK, libfyaml[0] (not libyaml) is the most spec-compliant library around. It's a shame more downstream languages aren't using it.

[0]:https://github.com/pantoniou/libfyaml
Re: the shopping cart example

> This approach is good for now. But, it will limit you later. Your code will quickly get out of control.

Will it? If we need to be able to “delete via X”, it sure feels more maintainable to have this feature supported via an explicit, named method vs. inlining it as an anonymous closure (as recommended by the “balanced” solution).
If we're not being pedantic, YAML has almost nothing to do with JSON. A typical YAML file and a typical JSON file have no syntactical overlap at all. Practically speaking, YAML parsers are expected to also parse JSON despite it being an otherwise unrelated format. The entire idea that it is a "superset" is misleading. This isn't a C -> C++ transition.
Ah, so the Netherlands and Cyprus, and off you go... If a third country is needed, a flirty wink to Luxembourg, and the party continues.
I think it's a perfectly good word for what is happening.
if all your internal headers start with cf- and most non-internal headers don't (but not all) and most headers are non-internal a trie might be hard to beat
How does this mixing happen? Consider the location of the deluge system and consider its right next to the ocean (which you really really shouldn't be drinking).

Do you actually think it plausible that any human could get sick when trying to drink their home water due to this discharge? Or are you just being contarian here?
> Binaries are much more capable than what I’m suggesting, though they are platform dependent.

Not if they're .NET/IL/CLR (which is an ECMA standard).
Three hundred reasons to not use Azure
This sounds like par2 with extra/different steps but I don’t know much about this space.

https://en.wikipedia.org/wiki/Parchive
Stack migrator here. It's phenomenal, and comes with a 2 week free trial. I would definitely recommend trying it out and seeing if you like it better.
This replaces AMX, it is its successor.

The older Apple CPUs implemented a custom form of AMX that was not standardized by Arm.

Presumably as a result of cooperation with Apple, the Arm ISA now includes a set of instructions with the same purpose like the original Apple AMX.

The newer Apple CPUs have been updated to use the standard Arm ISA, instead of their older proprietary ISA.

In the Apple CPUs, the former AMX and the current SME provide a much higher throughput than the CPU cores, even if lower than the GPU, and a much lower latency than the GPU, even if higher than the CPU cores.

AMX/SME is implemented as a separate accelerator, distinct from the CPU cores, because this saves power and area in comparison with implementing such instructions in each CPU core. The Apple CPUs do not attempt to compete in high-performance computing applications, so the extra throughput provided by a separate shared matrix operation accelerator is good enough for them.
I appreciate the write-up, it's very insightful. But I was quite concerned about the amount of response mocking being used as a solution. Did the team ever consider instead making upstream changes to jupyter-lab (which is FOSS), so that these requests are either deferred or can be configured to not run? That seems like it would benefit everyone, including your company - and might even uncover further optimizations.
cp and copy, and \ and /, etc. My sanity is preserved, however, by having the same editor on all the machines I use.

Although I can't get copy/paste to work in a remote text putty window. Sigh.
So, we agree, Mastodon do work
> But an accretion of kludges around an insufficient set of core functionality is absolutely worse than having a little extra functionality that you end up deleting later.

I agree that an accretion of kludges is bad. The problem here comes down to usually the skill of the programmer when the new work comes up. To people who don't understand the code, they are more likely to make what they think is a simple kludge than actually refactor to solve the problem "correctly", which usually involves more thought and creativity.

Whereas extra functionality usually increases the code surface area, and once published as a public interface to a library, is very costly and painful to delete. Then it festers as complications to new code that is added have to assume this extra functionality is used rather than not.
TBH I would love a pixel framebuffer standard for terminals that's fast enough to run things like Doom, emulators, or simple UI applications in the terminal. The Sixels standard exists but has a too complicated pixel encoding.
I have a lower end Samsung that “started” after I opened the door. I hope it was just the fan and lights like the article mentioned. But it scared the heck out of me.
It's very nice, love it
"... and then there are the unknown unknowns."
netip is one of the newer additions to the stdlib (added in ~2022), and follows the venerable stringly typed error idiom.

I always interpreted the preference for stringly typed errors as a way to keep the Go language simpler. Good error handling is complicated and hard to read, and one of Go's values is that programs should be easy to read. As such, if you want good error handling, you should use a different language, like Java or Haskell or C++. This also helps keep people who might demand complicated things like generics away from the language, further keeping it simple.

My understanding was that many of the go idioms are there to scare off programming language theorists, who have a tendency to unnecessarily complicate everything with type theory, and error handling also seems to mostly be in that vein.
It is not only for the pedantry, unfortunately. A subtle input that is a valid JSON but an invalid YAML may cause all sort of problems at any level, with some security implications.
As someone who is working on modernizing the command line, I think it is entirely possible to strike a balance.

- the command line is just byte streams

Shells like Elvish, Nushell, Powershell and my own shell, Murex, support typed pipelines and that brings a great number of enhancements. Like native support for JSON, CSV and other data formats. Thus meaning you can have a unified syntax for handling different files rather than remembering a dozen different tools and their specific idiosyncrasies, eg `jq`, `awk`, etc

- readline is dated

We can do better than the typical shell interface. The popularity of tools like `fzf` and `starship` show that people do actually find modern TUIs useful

- rendered text is static

Lets say you view a JSON file in Firefox, you can expand and collapse specific branches of that JSON file. I'd love to be able to do that with JSON in the terminal. And not just JSON, tools like `tree` could benefit from that too.

Collapsible trees is a feature I'm working on implementing in my terminal emulator and it's completely optional. ie by default the tree renders the same way any other terminal would render that clump of text. Except you can then optionally collapse branches just like you can with code in an IDE or comments in HN.

---

I love the command line. I've been using it for 30+ years and written so many tools for fellow CLI enthusasts. But even I think an ideal world would be us moving away from grid based virtual teletype interfaces pushing communicating via raw bytes and with in-band control codes, and instead switch to something more robust. But that's never going to happen. Heck, even things like job control (ie when you hit ^z) is non-trivial to implement at a shell level. It requires multiple signals (each originating from a different sender), and 3 different hierarchies of process ID registration. Frankly, it's amazing any of this stuff still works. And that's before we touch on the plethora of competing standards to test what client (ie terminal emulator) is connected to that "virtual typewriter".
Gru.ai Ranks First in OpenAI's Latest SWE-Bench Verified Evaluation
PSU Prices
I think I just miss being 14-ish when technology felt mesmerizing, and world seemed infinite because I was learning Pascal.

Now I just want to wake up, have my coffee, and not read about some new machine learning framework.
What's the problem with regulations aimed at US big tech? If something it came too late. And for sure they don't need ahmeneeroe-v2 to defend them online for free.
I think those who care about things being open-source care deeply about it and it is an issue that will make them avoid something. However, that is a very small group of people even in the tech world it's pretty small.

Businesses don't care if you're source-available or open-source and decision-makers often won't know the difference. Generally, people looking for open-source are just looking for something free they can use/self-host.
These require consent if, for example, they involve the use of a third-party service. Setting a first-party dark mode cookie does not require opting in even if it's "non-essential". It does however require disclosure.

The jury's also still out to what degree third-party cookies need to be disclosed in detail (e.g. whether you really need to keep track of the dozens of cookies Google Maps or YouTube sets or whether you can just refer to their privacy policy for the details). But embeds for YouTube, Twitter, Facebook or Google Maps, or the use of Google Fonts or the use of third-party CDNs for non-essential functionality definitely do require consent (i.e. opt in).
Maybe. But I'm not Russian. I know a Mexican called Ivan.

Anyway, there's no business as literally Link is just tokenized credit card storage - it serves them, not me. I use 1Password with Privacy.com, so Link serves them and does nothing for me. But I feel offended by their hostile and unjust action!
I agree about the distinction you made from the human perspective and you put it well.

I have always hated YAML, and still to this day, because I cannot write a yaml file, the indentation makes no sense to me and the list syntax is black magic (you actually have several ways to write those, once again the indentation implication is obscure). So while agreeing on the goal to be written/edited by humans to my perspective it fails at it.

Also 1e2 might not be the best example as this is just 100, but as someone who had to pass a lot of neural network training hyper-parameters : passing 1e-3 and so on is definitely a use-case. I am on the negative values Xe-XX (and YAML 1.1 would parsed it OK) but I guess other domains could also use the positive side to pass values (maybe as upper limits like 1e5 or so).

I think the YAML format should have parsed those number formats from the beginning. If this is fixed now, good job, hopefully the default yaml parsers are going to be "fixed". I would still use TOML over YAML any day, waiting for a human-json (some already exist) to be popularized one day.
Can we please stop this polarizing drama, from both sides? I never said that anyone wasn't cooperating. Quoting your link:

> > is there any update on the root escalation vulnerability in 2.24?

> Eelco is working on it, there's a patch on the GitHub advisory, we plan to get it out on Monday, but no promises yet if everything will get done by then

This is what I mean is not sufficient in terms of disclosure coordination... Doesn't seem like anyone was necessarily acting in bad faith, just mutual frustration and room for improvement on professionalism on all sides. Though I'd hold NixOS maintainers to a higher expectation of professionalism than random independent security researchers. The important thing is that people draw the right lessons. "The X people suck" isn't a valuable lesson for any value of X. And if you're seeing bad intent on the reporter and them trying to prove a point; well yeah, maybe, and point proven? Processes should cover for these eventualities.
This is why Textualize[1] concerns me. I've tried a few of the applications using their framework, and they have noticable keypress latency. I didn't think it was possible to make a bloated TUI, but they have somehow succeeded. This might just be a Python thing because of the GIL, because VisiData[2] has the same problem. It's physically jarring to use VisiData because it's such a cool idea, but takes 500ms to register key presses in my 120hz terminal emulator.

It's reminiscent of scroll-jacking, excessive animation, and other web GUI bloat, just translated to TUIs.

[1]: https://www.textualize.io/

[2]: https://www.visidata.org/
Often the notebook was run on a beefy server with GPUs attached, potentially taking hours/days of compute. It would be senseless to force every viewer of a Jupyter notebook to have the same setup and time just to read through the results and output.