skysight-inc/HackerNews huggingface dataset:
There are strong arguments on both sides, IMO. I especially agree with the potential for EU members to send the feed directly to their intelligence agencies' exploit development divisions.

The biggest gap I see in the open letter is this part:

"Require reporting to agencies of mitigatable vulnerabilities only, within 72 hours of effective mitigations (e.g., a patch) becoming publicly available."

There are a surprising number of commercial software vendors as well as open source projects that will happily sit on severe vulnerabilities[1] for many months, even years before issuing a patch. Some will ignore them entirely.

In a tiny minority of cases I've encountered, that kind of delay is justifiable. When I reported CVE-2023-21541 to Microsoft,[2] they asked for something like six months to build and test a patch, and I felt like that was reasonable, because fixing the bug meant changing the way Task Scheduler worked in a way that could potentially break automated processes (including Windows Update) across the world. It was also only meaningfully exploitable in corner cases outside of Microsoft's control.

Usually, it's not justifiable. I once sent a detailed writeup of severe vulnerabilities[3] in a widely-used telecom product to something like twenty people who worked for the vendor.[4] After literally a year of asking for status updates, they claimed that somehow all of them had lost the writeup and nothing had been fixed. When we pressed them further, they updated their documentation to include a statement that the recommended configuration for the product was behind a firewall.[5] No patch, no disclosure of the issues to their customers.

The suggestion needs some additional deadlines, IMO, or it completely defangs the EU's requirement. For vulnerabilities being actively exploited (not by good-faith researchers) vendors should be required to report the vulnerability to the EU either within 72 hours of effective mitigations being made available, or 7 days, whichever occurs first. For vulnerabilities reported to the vendor by good-faith researchers that would allow attackers to compromise instances of the product/service (or the underlying host/device), or retrieve sensitive data without authorization, 72 hours or 90 days, whichever occurs first. If a vendor can provide very compelling evidence, maybe allow them an extension to 180 days.

[1] The ability to execute arbitrary code on a remote system, obtain unauthorized administrative access, retrieve sensitive data belonging to other users, etc., with full exploit code provided to the vendor/maintainer.

[2] https://msrc.microsoft.com/update-guide/vulnerability/CVE-20...

[3] Unauthenticated remote code execution, hardcoded administrative passwords for almost every network service, etc.

[4] I worked for a customer of the vendor, and the report went to everyone on an email thread about the issues.
What if you live in US but your health doesn't allow you to drive a car?
Devil's advocate, but one might argue patents actually incentivize progress.

Without patents, there is far less incentive to seek progress. What's the point for a for-profit organization to spend resources on Research, just to see your innovation immediately copied?

And if said for-profit organization still innovate, it has a strong incentive to keep its innovation as secret as possible. Patents by contrast, incentivize sharing, on one hand it makes the innovation public knowledge, and on the other licensing agreements usually exist.

And in the end, 20 years is really short compared to human history.

Are patents an ideal solution? Hell no, this system is too easily abused (patent trolling, patent thickets, etc), and feels really wrong at times (patents on life-saving drugs for example). But so far, that's the best compromise we manage to mostly agree on in terms of worldwide IP recognition.
It is. I'm in Oxford, UK, where there's lots of public transport, but I've never seen a 6-year-old on a bus solo.
To be fair, between french from different regions, people will pronounce those differently or not, and not pronounce it the same way…
Another option is to use something like ws-butler[0], which only deletes trailing whitespace on lines you've edited. This way you don't create spurious diffs on version controlled files, which confuse code reviewers and `git blame` users in the future.

[0]: https://github.com/lewang/ws-butler
This is really interesting. I like the scoring system for each word. But if I can't pronounce one word correctly, shouldn't there be a way to listen to the right pronunciation?
Let's be real, default arguments are most commonly used because the programmer is lazy and doesn't want to update the function call in 200 places.
ElixirConf 2023 – Brooklin Myers – Exploring LiveViewNative – Talks
If someone is ignorant and (Re)uses weak password then it's own fault. Yes, phishing can happen but it's more convoluted (and again - lack of attention). Being conscious about it brings the benefit of not relying on single point of failure...
> Kotlin has a lot useless syntax sugar, for example @decorators are less powerful than the @decorators in python.

I think you're comparing two different things. Kotlin has "annotations", not decorators. It's because of it's java inheritance, where that is the way it's done. It's two different concepts. With a decorator, your code is replaced with a function call with the function itself as a parameter. With an annotation, you're just adding metadata and an annotation processor or static analysis tool etc can do whatever it wants with it. Like aspect oriented programming. You mark your code as having certain properties, and then other code can find it and react to those.

I don't know of much other useless syntactic sugar in Kotlin? I think most of it is quite nice, for instance how you can put the lambda outside parenthesis or create infix operator for more readable code. I also like the implicit `it` parameter in lambdas, better than what this article shows. Doesn't support multiple arguments, though.
> One of the most common criticisms veterinarians receive is that they're greedy. Doctors and staff are often asked to give discounts or waive fees, and owners can get upset when the answer is no.

Clearly, we need universal pet health care.
Bay Area high school grad rejected by 16 colleges hired by Google
Oh that’s helpful. I should look into setting that for TS.

Also frosting can’t be null when type is cupcakes. We found a bug.
In practice, you wouldn't use |u| either. You'd use |user|. I would only allow single character variables if they are scoped entirely within one line of code. But even then, best practice is to use good variable names, so I'd still prefer `users.map{ |user| do_something(user) }` or whatever. I use the to_proc pattern for existing methods on the object like `users.map(&:email)`.

The only case where I've used a shorthand pattern like _1 is with regex matching where the matched groups are not named, so $1, $2, $3 refer to the first, second, third matched groups, etc. Having worked a lot with csvs (mentioned in an example), referencing the header (or creating one) has always been really valuable, using numbers is asking for trouble when the spec inevitably changes or when a dev wants to know if a script will work with some new file.
I used Delphi in the 90's and early 00's, and really loved how simple it was to create desktop applications. I tried to get back into Pascal via Lazarus a few years ago, but was just very turned off by Pascal itself. The conventions just differ so much from other more popular languages that I use for work now, and there just isn't the same level of stack overflow questions/answers to make it easy to pick up. I guess with ChatGPT, it should be a lot easier to pick up now, so maybe I should give it another go.
In another comment you said this was 3-4 years ago, and by that point apparently this had been running "several years", which one usually takes to mean 3 or more years, so in total 7-8+ years ago at least, which I rounded up to 10.

For what it's worth, I'm not accusing you of lying, I'm making a tongue in cheek observation about altcoin exchanges.

It does seem like you are stating the MTM valuation (i.e. spot x notional) without mentioning liquidity, which is where the confusion from others is coming in. It's very possible to accumulate a large position in a low liquidity altcoin that you will have zero hopes of selling for that valuation, even over time.
Hyperkit – Figma UI kit to help you craft any web app design project
Hopefully we never have to use Python again after this and it goes the way of PHP. The only thing Python really has is ML/AI/stats.
How did they produce the nitrogen gas?
This. It’s also very possible people can get long COVID from COVID, but it’s exacerbated and/or more likely for those who are vaccinated
Let the security community send their reports to the governement, in exchange for indemnification.

If the gov gets bothered by too many useless reports, I am sure they can deal with the reporter.

In fact, an active security incident is a crime. You can as well report it to the police,it's basically the reason they exist.
Both APIs are not all that great, Vulkan has a steep learning curve and requires tons of boilerplate code to even get a triangle on screen, and OpenGL is 30 years of sediment layers all pressed into a single 3D API.

WebGPU is currently probably the best balance between:

- easy to learn

- easy to tinker with (in web browsers at least)

- modern concepts (close enough to Metal, Vulkan and D3D12 that what you learned carries over)

- platform-agnostic

If you are on Windows, D3D11 is also a good native option, as is Metal on macOS.
This article reads more like an ad for mORMot 2 than Pascal. I've been out of the Pascal game for a few years, so I had to look up mORMot 2.[0] Apparently Synopse are the maintainers of it.

The article basically compare their CSV/JSON serialising library to Go's standard CSV/JSON libraries. Looking at the Go code, it's pretty clear why it has memory issues, it reads all the lines into a single object (well, `[][]string`) immediately, rather than reading line for line (which takes advantage of the stream).

I am not sure how this is remarkable and impressive for Pascal. They talk about how you don't need to use the `try..finally..Free` routine all the time, but that's only if the object in question is an interface. Interfaces are somehow handled by a reference counter in Object Pascal, so you need to know how to operate on objects vs interfaces, because they act very different. Pascal is full of these quirks.

[0] https://github.com/synopse/mORMot2
What? Companies like Microsoft have their own recruiters.
Again, that's just the inner developer not liking the term. There's a reason why AI sticks with people and ML doesn't.
You need to have someone, or a group of people, willing to write the code to implement support for modern tooling on their platform. Until then, old harder-to-secure codebases is what these platforms have.

I know reversing the burden of implementation seems flippant, but it's pragmatic. At some stage, it's less community-wide work to support Rust on a new platform than to spend extra time maintaining/securing dozens of C codebases. Curl may not be making its Rust components mandatory anytime soon, but other projects like python crypto already have, to say nothing of projects written in Rust to begin with.

rustc_codegen_gcc is pretty close to ready, let's focus on getting it out of the door, and more target triples supported by rustc and llvm.
"Just passing a function" is incompatible with Ruby's current syntax where a bare method name calls the method unless you then introduce a way for method definitions to defer evaluation of its arguments, but then you open a can of worms given that Ruby allows aliasing and replacing arbitrary methods of already defined classes. I suspect it'd be a nightmare of inconsistencies.
Canon EOS M can be bought for around $100 used and shoot 1440p raw with Magic Lantern. Also it can use cheap old 16mm film lenses with crop mode.
I made a small nod towards Haskell's way of doing things in the last paragraph of "How others do it" section:

> We might also start look into the concept of the “tacit programming”, which, from some point of view, is also about “not repeating the arguments,” but this would be a much longer post—while it is obscenely long already.

Note though that my analysis was mostly about "how you would do that in an established language," not "how would I design a language from scratch." And Ruby is very different from Haskell in its syntax, semantics, and typical intuitions of the language writer and reader.

So designing a solution for clearer representation of "default parameters" is quite different in a language which is built around an `object.method(argument) { block }` as its atomic phrase, and one built around `function(arguments)`. (This can turn into a discussion of which phrase structure is more elegant in general... But I believe it was already done quite a few times in a history of programming languages evolution!)
It usually boils down to religion. I don't think converting people to atheism has a high ROI.
Croatia wants to turn superhot underground lake into 16MW power plant
exactly, in the context of "de" and "deux" depending on the person (native or not) , you won't be able to differentiate the pronunciation without context
"It makes the whole world afraid of what is in fact just matrix multiplications" is such a reductionist view that doesn't really capture the reality of AI taking people's jobs and reshaping the economy. That's like saying electricity is just "electrons moving through a wire"
If you read the article, they developed their own(?) lxpanel clone for Wayland apparently, so there's some custom work there. Of course I wonder why that wasn't done upstream (or maybe it was, and it's just not spelled out).
Without commenting on the merits of this technique, composting is as old as the hills and doesn't necessarily involve fossil fuels.
You have an oddly efficient view of "government agency sues $company for doing obviously horrible thing." These lawsuits drag on for ages, become huge political battles, and are a just a huge expenditure of resources for everyone involved that it's saved as a last resort.

I don't think you would like living in a world where things like this could be settled swiftly and decisively. Having a government where voluntary compliance is the expected norm and applying real force takes time and resources is a feature not a bug.
> "The moral is that a utopia where tolerance for plurality is permitted is ideologically incapable of defending itself from external threats."

See also the Paradox of tolerance[0]: "Unlimited tolerance must lead to the disappearance of tolerance. If we extend unlimited tolerance even to those who are intolerant, if we are not prepared to defend a tolerant society against the onslaught of the intolerant, then the tolerant will be destroyed, and tolerance with them."

[0] https://en.wikipedia.org/wiki/Paradox_of_tolerance
Is it better than llama 2?
Not a junior analyst dog, no.
Opus hasn't caught on for music and podcasts, but is very popular in some other areas. YouTube uses Opus heavily, for example, and its the default audio codec for webm video files. It's also very popular for real time audio like in video conferencing.
This is actually exciting. Converting carbon free energy (such as solar and wind) into chemical energy is I think one of the more promising approaches. One of the big challenges of solar and wind is matching instantaneous supply with instantaneous demand.

By converting it to chemical energy, you can basically take the solar output that you get and use it. If you get more, you produce more, if you get less, you produce less. It is adaptable to the supply.
I just put them in a central place, personally:

(setq auto-save-file-name-transforms '((".*" "~/.emacs.d/autosave/" t)))
(setq backup-directory-alist '(("" . "~/.emacs.d/backup")))
As someone who works in the field and works with LLMs on the daily - I feel like there are two camps at play. The field is bimodally distributed:

- AI as understandable tool that power concrete products. There's already tons of this on the market - autocorrect, car crash detection, heart arrythmia identification, driving a car, searching inside photos, etc. This crowd tends to be much quieter and occupy little of the public imagination.

- AI as religion. These are the Singularity folks, the Roko's Basilisk folks. This camp regards the current/imminent practical applications of AI as almost a distraction from the true goal: the birth of a Machine-God. Opinions are mixed about whether or not the Machine-God is Good or Bad, but they share the belief that the birth of Machine-God is imminent.

I'm being a bit uncharitable here since as someone who firmly belongs in the first camp I have so little patience for people in the second camp. Especially because half of the second camp was hawking monkey JPEGs 18 months ago.
Thanks for sharing that. Coalton looks pretty cool.

On the SBCL side of things, a quick skimming of https://lispcookbook.github.io/cl-cookbook/type.html doesn't paint a very pretty picture. The syntax looks a bit verbose, and the error seem to be very rudimentary, not worded well, and lacking even a line number. Overall, the readability of the Common Lisp code in this link (as someone who doesn't know CL) honestly doesn't seem to be great. Hopefully, if someone could distill and write about some of the key language features that make CL great, we could carefully transplant/copy those features into a modern type-safe language.
I like this! I am surprised to find out my accent heavily leans towards the US's despite me being an Indian. Then again I grew up watching a lot of American movies, it's not really a surprise.
This must be highly cultural. After you done the interview, shook hands and thanked the interviewer there in person there is little point of follow up other than an opportunity of reminding of yourself in the consideration process.
1908?
Some people complaining on Twitter too: https://twitter.com/ContaboCom/status/1712062706784543080

It looks like ALL their VPS are down.
A bit strange that their user panel is down too, maybe it's hosted on their own VPS infrastructure.

I understand downtime happens, but communication so far is terrible with Contabo. There have been outages before and they were never registered in their status page.

EDIT: Seems like they added it on https://contabo-status.com

> We are experiencing a disruption in our Nuremberg Data Center. We’re sorry for the inconvenience.

> Please follow the updates on contabo-status.com and avoid contacting support right now. We are all focused on investigating the issue. Next update will be published at 19:00 CEST.

So, the next update is in 3 hours. That's a long downtime window.
The business fundamentals and the emotional reality seem to be inherently at odds. I'll bet that this is a leading indicator for what's gonna happen in people medicine.
As a car analogy, OpenGL is a Toyota. Vulkan is the pieces to a Ferrari.
I feel the same comparing my iphone and mirrorless. It's obvious software is years behind in almost every aspect; even relatively easy fixes like the horrible designed and unintuitive UI choices where the same mistakes are made year after year despite complaints...ugh! The last thing I need when taking pictures is fumbling around in 5 layers of menus to change important settings while my subject moves on and the moment has past. It almost feels on purpose as if the though is that added complexity is some proxy for it being "professional"

If processing power is one of the bottleneck to get some of the features phones can do it would be great if there was a universal hotshoe-like way to mount phones to camera bodies to use the screen, touch capabilities, and offload processing power, maybe with all phones now having USB-C its more of a possibility. If the camera makers don't do it I wouldn't be surprised if Apple/Google eventually do and eat their lunch.
I think this further supports the point about the unfathomable cheapness of life before the 1900's.
The Challenges the IDF will face in Gaza
Next time you are in Munich, take public transport of any kind between 7 and 7:30 in the morning on a normal school day, there are sometimes morw school kids of all ages in a given subway car than adults. Pretty funny to witness, seeing the little ones behaving like all the adult commuters, head phones and all until they meet their friends.
I think for there are two already okay options. As Syncthings UI is already in the browser, one would be to just host that page in a way that it's remotely accessible (e.g. in you VPN, where I can highly recommend Tailscale). The other would be to use the option that Syncthing has built in to auto-accept folder invites from certain devices (that's what I have set up on my always-on server so I don't have to SSH into it every time).
The moving away part is taking decade of slow and confusing but still huge progress indeed.

And as other have stated the absolutely CRUCIAL question in picking your API, is going to be :

what do you want to do ?
So was almost every unicorn startup. They purposefully aim for growth until its unsustainable, then switch over to exploiting their market position. We may not like it, but the business model is far from novel or unexpected.
That is where exceptions come into play. Yes people with disabilities (which could include elderly people) will need a different form of transportation.

But exceptions to allow those that need it to drive or other services (like grocery delivery) can take care of that while still allowing for a pedestrian focused city.

There is also the fact that if a city is properly designed ideally you may only need to walk a couple blocks for groceries and your basic needs, and instead of doing big shopping you buy just a few things at a time.
If you are looking to dig into Metal, this site and book might be useful. I have no graphics background and found it accessible.

Metal By Example https://metalbyexample.com/
`ii` it is then
I once asked for a feedback, was told that they won't give any. Filed a GDPR request and got all of their e-mails and internal tickets about me and my application. Funnily, they printed this data, scanned to PDF and sent the PDF via e-mail.
It's just the name of the taste of monosodium glutamate, pretty much.
If you lump abjads and alphabets together, the Ugaritic alphabet represents another invention of an alphabet. Instead of being derived from Egyptian hieroglyphs, it's derived from cuneiform. Old Persian cuneiform, another invention, is also largely alphabetic, with only 9 of the 22 consonants being routinely written in forms that also include a vowel.
It is better than llama 2 7b and 13b. I tried the OpenOrca fine tune and it is very good, even when 4-bit quantized
It is quite useful; and if you read many HN comment sections, you will see it often.
Libraries with individually owned bookshelves spreading in Japan
Even if you go by number of trips and then even if you limit yourself to just trips 3.7 to 7.5 km cars are still are 50% more common than bikes.

https://www.cbs.nl/en-gb/figures/detail/84708ENG
All the articles about LLMs passing different exams isn't helping. LLM can pass exam X etc..

Of course it can pass exams, so could a database storing the answers.

Ask it to try multiply two floating point numbers though and you often get the wrong answer.
It was the IS II at the time, but yes - an absolutely spectacular piece of kit. I think it was about $100 to rent for the weekend? Very reasonable IMO, and made me realize that one could quite easily bootstrap a wedding photography business without actually owning gear.

Other than the actual business side of things, pesky details like getting clients. And the massive stress of shooting a wedding. I was happy to do it gratis for family, but I don’t think I’d want to deal with paying clients.