skysight-inc/HackerNews huggingface dataset:
IMO benchmarking is a way broader topic.

Specifically a single fibonacci example is not a good performance indicator by any means.

For instance let's assume V8 is faster in average at running this kind of nanobenchmarks (probably at least for now it is), but how much does it cost to convert non trivial data structures from Lisp to JS and back in a real case?

I expect there will be a lot of back and forward if the system if JS and Lisp get mixed and have to cooperate.

How much does it cost to go through foreign functions calls?

This are just initial thoughts that are not accounted at all here.

And even benchmarking nano-benchmarks can be surprisingly tricky ;) :) https://github.com/emacs-ng/emacs-ng/issues/187#issuecomment...
I don't think the release cadenece (6 weeks) is the cause for how fast the language was changing.

As a counter examples, Go release roughly every ~26 weeks and mostly has releases with minor updates. Chromium releases every 6 weeks but not every release has major updates; they are mostly bug fixes and minor improvements. Even Android is decoupling its system services into components which can be updated through the Play store at a much faster cadence than their yearly releases.

I agree that Rust needs to now focus on polish over new features at this point, but I'm not sure that Rust should've done something differently, especially around its release cadence. I don't think it would've been a good contender for serious companies if they hadn't invested heavily in async, for example.
A lot of EU countries suffer from youth unemployment. If you can't even get them to work today you won't get them to work by the time you retire.
It looks like the chain here was 'visit some site via browser' -> 'kernel exploit' on ios, windows and android.

I'd call whoever is responsible for such a valuable amount of 0days expert/nation state level for sure.
Current Sensing using embedded TinyML models
Just check the issue tracker for what kind of things he is working on: https://github.com/curl/curl/issues

Curl has 170k lines of code, so it's bound to require some maintenance.
Well, its not so much a direct part of The Baroque Cycle as a continuation using descendants of the main characters and a lot of shared themes - a bit like Cryptonomicon.

However, The Baroque Cycle does have some unusual minor elements such as 'magical' gold and an important character, Enoch Root, who appears to me immortal and who turns up in 17th, 18th, 20th and 21st centuries.

Fall gives an explanation of what is going on that I really liked.
See this for how it actually works in code: https://chsasank.github.io/concurrent-programming-trio-tutor...
If a PC is infected I can (and should) reinstall everything from scratch. That should remove the malware, barring some super resistant malware that hides in the BIOS or something like that.

What do you do on an iOS device? Does a full device reset reinstall the OS, or does it simply remove all user settings?

I feel like the locked down nature of iOS makes it harder to attack, but if an attack goes thru it would also make it harder to clean up the attack?
The point is that comments (in regard to the article) are littered with anecdotes about cyclists getting in danger because of cars. It's a one-sided view. There's problems on both sides equally. Conflicts of this kind are waved off as "the driver was an asshole", which might be correct in single cases, but misses the whole point of the actual problem completely.
It's quite funny that this is a bunch of complaints that they can't keep up with rust development and that they should do things differently but ends with a plug for their book about their experience programming in rust.

I was under the impression that rust is pretty stable?

Like web browsers get updates on a fast cadence and it rarely breaks existing web pages.
For the people as confused as me, it stands for "Insecure Direct Object Reference" and not "International Day of Radiology" or "Iowa Department of Revenue".
Ha, interesting!
Would you be interested in sharing more details? (How you got in, for exwmple)
I am guessing, because of the complexity of the problem. With the previous way of doing things I am guessing youtube either push all the videos that get uploaded in to some queue to detect copyright violations, or once a video reaches a certain number of views the copyright algorithm gets triggered.

With the new system I am guessing they have to do this thing in real time and almost anything real-time is a complex problem to deal with right?
Click bait article with minimal substance that pitches a book sale? Feels like spam? I guess the topic gives everyone yet another chance to air their hypothetical greviences with rust
Cool stuff. Well presented. Just by coincidence was just reading this yesterday: https://vivonomicon.com/2020/06/13/lets-write-a-minimal-risc...

nMigen is super interesting but I'm still stuck in Xilinx Vivado as a beginner because it makes integrating small cores so easy. Full RISC-V SoC that does something useful in the FPGA part and runs a small version of Linux and programs that call the FPGA part would be super neat.

Seems small RISCV cores can be written very quickly https://github.com/darklife/darkriscv#introduction, but actually making them production hardware take a long time: https://zipcpu.com/zipcpu/2021/03/18/zipos.html
Maybe a better link: https://googleprojectzero.blogspot.com/2021/03/in-wild-serie...
You already lost the moment you are born.
It seems that a watering hole attack by definition targets users of a particular organization, but articles on this event make no mention of which organizations would that be, sounding like it affects general public. Wondering who should be worried.

Related: can community recommend some forums, periodic publications or other sources that aggregate information security news?
Going on the street without paying attention to all signs, rules and potential dangers is NEVER OK. That's paramount (for everyone on the road) and I'm not questioning that for a second.

That said, bikes are dangerous for everyone involved. If you encounter a bike you slow down all traffic (because you can't overtake safely, and that's difficult on busy roads), you have to keep distance and account to the fact that you could run over the biker AT ANY TIME because bikes are NOT reliable when roads are not 100% correctly maintained. They can stop at any time on the road for some reason without even a warning, and as soon as you touch them they're pretty much dead. That's enough to give any driver a 500% stress increase. And I'm sure for the biker is the same.

I know I sound like an asshole but if drivers hate cyclists, and pedestrians hate cyclists, and motorbikers hate cyclists, and public transport drivers hate cyclists, and truck drivers hate cyclists, and politicians hate cyclists... I'm not saying they're right, but for sure there is a recurring reason that's worth investigating.
The license these businesses should be using is AGPL, clean and simple.

Run the software under AGPL and dual license it under a closed or restricted usage license if a customer doesn't want to use the AGPL license.

Instead we have people electing to create restrictive licenses with varying degrees of "use the software however you like unless we don't like you or your business" baked into them.

The dual full free + restrictive license model has worked very well in the past for FOSS based companies. Let people who are fine contributing back to your project and/or open their project up use it however they please and let everyone who doesn't like those terms pay for it like standard commercial software instead.
Rust has a release every 6 weeks, but there haven't been any new major new features in stable since async await, which was in November 2019. The situation is not too different from Chromium.
Totally agree, this is what killed rails in 2.x time for me. Anytime I finished a feature half the packages were out of date and incompatible.
My personal take is that in our globalized world, the governments are in competition to some degree for corporate tax dollars and that pushes corporate tax rates down, but they are all independently doing that with the goal of maximizing their own income.

I can respect anyone on any side of the aisle as long as they admit its a complicated problem.

But I will hold that if the US went too high with its number, at some point it would have really negative effects for the country. I don't claim to know what that number is and I assume it is to some degree relative to the rates that other countries have and to some degree relative to whether companies are netting profits or not.
Algorhyme
Docker for Mac M1 RC
Free Weekend at Vue School Master Vue.js
Free Weekend at Vue School 27th - 28th March 2021!

We’re unlocking The Vue.js 3 Masterclass to watch for free. Learn how to build a real-world application from scratch with our signature course and explore the latest Vue 3 features.

The course is worth $329 and it will be free for a weekend only!

Reserve your spot today! You’ll also get access to an exclusive discount
https://vueschool.io/free-weekend/
> Take your queue from some of these shows. None of the people in them are watching 3 or 4 hours of TV a day.

It's because 99% of commercial shows and cinema depict a fantasy. In reality, most people in developed countries watch TV/streaming for multiple hours a day. If you want to take cues from shows/movies, try watching the art ones instead, they are often closer to reality and are fine with showing the unpleasant truths.
Youtube also has very different quality within the same language. For Brazilian Portuguese (easier variant to parse) recent videos are decent (if it's normal speech, not songs or fiction) but I found some from 2017 where it was garbage.
Rust has lots of nonsense with zero practical benefit. Examples: PhantomData, higher-ranked trait bounds, "upstream crates may add a new impl". I have satisfied the compiler but no bugs were prevented. It's just busywork.
Did you stop reading at that bit?
Impounding the driving license and/or car for a limited period of time could be a more egalitarian, privacy friendly and easier to implement alternative.

Your idea of some form of progressive rate punishment sounds really good. Time is probably the easiest to implement parameter:

- impound_car(time)

- impound_license(time)

- impound_license_and_car(time)

- impound_license_and_all_cars_owned(time)
Pac-Man in Excel: https://github.com/spences10/pacellman

More Excel games at http://www1.plala.or.jp/chikada/index.htm (in Japanese. Google translate: https://translate.google.com/translate?hl=en&sl=ja&tl=en&u=h...)

I think ‘real spreadsheet games’ shouldn’t use VBA, but I also think that rules out arcade games with decent UI (you can animate by using iterations, but I think user input would require the user to hit enter to register commands), so, maybe, one should allow some minimal VBA in a subcategory of spreadsheet games that don’t use the spreadsheet’s scripting language)

Edit: I didn’t test it, but it seems using https://support.microsoft.com/en-us/office/cell-function-51b..., one could have a mouse-operated VBA-less Flappy-Bird that reacts to the user changing the width of a column, or use cut and undo to delete or reinsert rows or columns, thus providing user input. That’s workable for some value of workable.
Rust has a very strict backwards compatibility policy, and as a result has had ~0 breaking changes since 1.0, with the notable exception of opt-in Rust 2018 edition. Best practises might get out of date, but generally speaking nothing breaks between releases.
I am hard of hearing and need captions on everything.
Why Technical Support Services Are Crucial for Your Business?
Interesting. I never knew that.
Due Diligence Checklist for Investing
This is what I love about Hacker News. There is an article, and there are reasoned objections to it in the comments, which means I can make a bit more of an informed opinion myself. Thanks all!
glorious <3

Must .. resist .. temptation .. uughgggh...
> That said, bikes are dangerous for everyone involved. If you encounter a bike you slow down all traffic (because you can't overtake safely, and that's difficult on busy roads), you have to keep distance and account to the fact that you could run over the iker AT ANY TIME because bikes are NOT reliable when roads are not 100% correctly maintained.

Going slower isn't unsafe, it's safer.

You're confusing inconvenience for lack of safety. Going slower and driving as if the vehicle in front of you may stop at any time is safe, responsible driving.
And how quickly do compiler/language bugs get fixed...
Absolutely awesome! I'm impressed by the level of polish, this is waay beyond the usual POCs you see for hacks like this.

For me, the tl;dr from the technical explanation was this:

> Now, everything in fontemon is baked

Just reading that made me laugh out loud. It's so simple and so ridiculous, i love it.

I recommend reading the entire blog post btw, it's very thoroughly explained and it assumes no knowledge of either fonts or gamedev.
I can't talk about python, but it's convenient to be able to cast something to any in typescript and get all the flexibility of javascript, but also have the rest of your code type checked if you want it. Statically typed languages usually don't let you mix-and-match static typing with duck typing.
Hey you don't own the streets so if someone slower is in front of you, you might just slow down for a while and don't give a damn about slowing traffic. Better safe than sorry.
And for that matter, why didn't Kristoff ever tell her that he'd seen her as a child and that she'd gone to the trolls before.
Javascript has no real competition. People have accepted its existence as a given so every improvement over it is celebrated. On the other hand, many languages want to be the new python and their fans will try to bring it down at every opportunity.

Note: I'm a python dev, yet even I can agree that the python ecosystem is broken and if not maintained, the language will decline over time.
As others have written, there's basically no connection between Rust's six week release cycle & the rate of actual change to Rust. If Rust switched to a 12 week release cycle, all that would change is that it would take twice as long for features to reach users on stable once they were decided to be released. Feature development is neither release driven nor release constrained.

However, the ground truth is that the design of significant new language features basically stopped in 2018. The work now is shepherding through the language extensions the project already committed to in the first few years after 1.0. For example, const generics, which will have a stable MVP in the next release, was first begun in 2017. Generic associated types, which are still not near stable, in 2016.

And my own view, these remaining features are a nearly "feature complete" Rust. Future extensions will be either more niche (a lot of attention in the last few years has been aimed at features to make writing unsafe code less error prone, which wouldn't visibly impact users who write only safe code) or less substantial (such as a syntactic sugar that would improve a lot of users lives, but not deeply change how they write code). And that's actually very good.
What Hacking Is Like
That happens to me even on YouTube. Every couple of months I have to fix the language setting and switch back to dark theme. What can't be fixed are Google's weird attempts at auto-translating video titles from other languages, making me click on videos that I simply cannot understand. Don't do that, Google. Do full title, thumbnail and video translation with 90% accuracy or just...don't. Half-assed tech is easy but not helpful for anyone.
I'm out of the loop: what's wrong with Daily Stormer?
I would just see it as trying to make a best product and using their expertise to achieve it.
The scare quotes in the title read as sarcasm but they clearly didn’t intend them as such. An odd choice as I almost overlooked the article assuming it was a tale of some failed hackers.
This article reads like an episode of Black Mirror. What is wrong with India...

This whole practice is despicable. And extremely predatory on the uneducated masses. Wouldn't be too far-fetched to see shady companies buying this data and re-targeting the same customers with other dubious financial products and loans.

Lauded for being one of the most progressive countries in internet infrastructure & access, the government of India is sleeping on this if not outright colluding with these unscrupulous corporate scammers.
The normal way to deal with this is to either not loan money to people that you don’t trust to pay back, or to account for the risk in interest.

Lending money to people and then strangulating them when they don’t pay is the way the mob works.
> I almost don't care about performance (at this point) as I know that could be attainable somehow once a solution is fleshed out

It rarely is though.
Ants are used for computation in "Children of Time" by Adrian Tchaikovsky. Really good story.
Most cyclist activists that I know advocate for separate infrastructure for bicycles precisely because being on the pavement is unsafe for pedestrians (and annoying for cyclists) and being on the road is unsafe for cyclists (and annoying for cars).
Up Your DevOps Game: It’s Time for NoOps – Devops.com
>"we figured out how to relax type checks to allow this safe program to compile that was previously failing to past muster with the borrow checker"

While perhaps not a large change in practice, this seems like the sort of thing that incurs a large cost when it comes to updating your mental model of how the compiler works, what it can and cannot do, and what options you have when it comes to implementing something.
How long until we realize that JIT was a mistake and that we should offer orders of magnitude slower JS in browsers that is actually safe (or start building webpages without JS at all again, which will probably never happen) lest we give every website the ability to take over our device?

I'd pay real money for a browser with a slow, safe JS interpreter.
The results are visually striking but also to be expected if the sensors already captured the necessary data (to the computer) and is obscured (to the human) by the relative (instead of absolute) perception.

What I find innovative here is the concept of thinking about anything that is hard to do as a human (night vision) but for which we can affect the state of (in this case, the light switch) in order to train a model to overcome the difficulty.

Sorry to belabor the obvious but I thought it was worth a description which may motivate other use cases.
There has been concerns about Other vaccine as well. Norway had raised concerned about vaccine safety after 29 deaths. We must understand that all these vaccines have been used for emergency situation. Fact is that no vaccine has 100% efficacy.
I've actually found Rust to be extremely stable since I started using it 5-ish years ago. I haven't had as much time to keep up with new features recently, but all my old code still builds as easily as it always did and the way I used to write code still works fine. I don't imagine I'm missing anything huge and transformative, and I tend to find new-to-me features on an as-needed basis through docs and web search.

It is kind of annoying when big libraries that are generally touted as the way to do X require nightly, but again that's my experience as of years ago. Nightly should be understood as a place where churn happens. For me, stable releases have never been anything but what it says on the tin.
I think Rust's biggest threat is that it's repeating the same mistakes C++ did, despite the hindsight. C++ tried to be everything for everyone -- a language elaborate enough to write applications in a style that appears high-level on the page, and yet not give up on the full control required for low-level programming. For a while, it worked. The problems only became apparent some years later, when large applications had to be maintained, and people realised that low-level languages, no matter how high-level-looking, all make a certain sacrifice: low abstraction. Clients of components are sensitive to implementation details of those components, and so the maintenance of applications costs as much as that of low-level code does. OTOH, the complexity of the language made portability hard (low-level code is often written for custom hardware) and also hard to analyse. C continued to dominate the embedded space, the application space went to true high-level languages, and C++ kept an intermediate, though important niche, of games and software platforms for capable-enough hardware, which it firmly holds on to.

Rust is now doing the same. Few in the embedded space find it appealing, many of those who use C++ do (as it is certainly a cleaned-up C++, and a nice improvement in comparison), but too often not appealing enough to switch now, and some in the application space who don't know or don't remember the C++ lesson do adopt it now (sometimes out of sheer novelty) but will likely abandon it later for similar reasons C++ was largely abandoned in that space. So it is really competing for a pretty small and conservative niche -- albeit an important one -- and one with a strong incumbent. If it does very well, in 20 years we might find that 60% of the C++ space has switched over to Rust, and that's about it.

What Rust needs is focus, but it won't have it because I think some of its designers still believe in what C++ believed. That you can have a language that is both high-level and low-level, with the benefits of both and the downsides of neither.So it's being pulled in multiple directions, all while showing poor performance in the market (C++, at least, wasn't just hyped but actually popular). It's not even going after C++'s market seriously, but after the nonexistent market C++ thought it could occupy; the only market it seems to be actually competing over and doing well in is HN-front-page real-estate, the space formerly occupied by Ruby and Haskell. When I was at University in the late '90s, everyone was talking about Haskell will be the language of the future. With almost constant levels of hype, more than twenty years later, it still is. It turns out that for various reasons, when it comes to programming languages, hype and market performance can be completely out of sync for decades. Rust's designers need to choose between adoration and actual popularity. The latter will require some tough decisions. If it's going after the C++ market, it should make itself extremely appealing, irresistibly so, to C++ programmers.
Or sex work is going to go be very lucrative as casual sexual relationships incur more of a tax if there is even the slightest bit of confusion on consent (not to mention the fact that most people have alcohol in them, some have drugs, others just have bad experiences and carry regrets...).
Thanks! For better or worse, I'm a perfectionist with deadlines (to steal django's slogan) . I tried to make everything as accessible as possible, because I know 12 year old me would want to make his own font-game. I spent a lot of time, adding guard rails to Blender so you can't get lost (I made it impossible to change the camera, to dismiss the side bar menu, I also made it so you never have to go into a sub-menu. Everything you need is available in one central location.)