skysight-inc/HackerNews huggingface dataset:
Long before the govt steps in, people will have stopped working hundreds of hours a month for an organization that hasn't paid them.
i think they are, it's just that the spreadsheet they're using is one they wrote themselves
I think, like OP that:

> I've searched around and so far mostly found click-baity type articles like "10 ways to do better technical writing".

So I hoped that there has to be a better way or silver bullet somehow.
> If you actually want practical and safe self driving cars widely deployed

That's a big if ;)

Not to be a luddite, but we are many that don't enjoy our cities being designed around car usage. That they take up all space that could have been used for nicer things.
Scientists discover new code governing gene activity
After it blows up the first time, intentionally or unintentionally, there is a much lower likelihood of it blowing up again
Also worth noting there are benefits to exposure that are often not full unaccounted for when considering exposure: https://www.ed.ac.uk/news/2024/uv-rays-may-boost-health-in-l...
Right, one winner doesn't change the odds... but we are choosing to throw out all the scenarios where that winner doesn't win, which DOES change the overall odds distribution. We are changing our selection criteria.
This would work if we had the ability to deny licenses to people, which would require us to have a real alternative to driving in more cities :(

> And I piss off a lot of drivers. Traveling the speed limit in the right lane in low density traffic, I will be tailgated or worse. Yet, while mostly driving well within legal parameters, I make good time and often end up ahead of erratic impatient drivers.

The impatient drivers overtake me but curiously I've never gotten a single ticket nor been in a collision. (I was forced off the road exactly one time)
As a Firefox user myself, yes! We plan to launch for other browsers after open sourcing MinusX (in ~1-2 weeks).
I feel like I have to disagree, even though I really don't want too. This technology is seriously overhyped.

We have to realize that there is a ton of money right now behind pushing AI everywhere. We have entire conventions for leadership pushing that a year later "is the time to move AI to Prod" or "Moving past the skeptics".

We have investors seemingly asking every company they invest in "how are you using generative AI" before investing. We have Microsoft, Google, and Apple (to a lesser degree) forcing AI down our throats whether we like it or not and ignoring any reliability (inaccurate) issues.

FFS Microsoft is pushing AI as a serious branding part of Windows going forward.

We have too much money committed to pushing the idea that we already have general AI, too much marketing, etc.

Consumer hype and money in this situation are going to be very different things. I do think a bust is going to happen, but I don't think in any meaningful way the "hype" has died down. I think and I hope it will die down, we keep seeing how the technology just simply can't do what they are claiming. But I honestly don't think it is going to happen until something catastrophic happens, and it is going to be ugly when it does. Hopefully your company won't be so reliant on it to not recover.
This is the robot.txt-ification of entrenching OpenAI.
No, like Lancet or Cell.
Many of these are at stage 3 of the standardization process and have a good chance of shipping soon: https://github.com/tc39/proposal-iterator-helpers

(They're not on objects, which I think is probably for the best; every method on Object.prototype is a shadowing risk and so we're unlikely to see any besides the ones that already exist. You can always use Object.entries; if your object has so many dynamically-computed properties that eagerly collecting them is a performance concern, then it should probably be a Map.)
For consistency, the same design problems should have the same design solutions a.k.a. pattern. If you don't value consistency, feel free to take a different approach every time. That will confuse your users. I used to work with a guy, the simple problem of reading a CSV was done using a library, problem sorted. Out of sheer excitement he then rewrote it was with combinator parsers, then as some astronaut architect functional monstrosity, so complex no one else could comprehend it.

This is how not to do it – for same problem, use same solution. I admit that's an extreme case but it's also a real one and illustrates the issue well.

(also patterns are not specific to OO, nor is OO incompatible with a functional style)
As other commenters have mentioned, MIT paying for articles a la carte worked out cheaper than getting all-access subscription from Elsevier. Presumably Elsevier would want to stem this sales channel so institutions would be forced to pay more.
quick! go to publishing before they beat you there!
Thanks. First time I heard of this. Without knowing all the details, at first sight I thought pig butchering had something to so with manufacturing pork. Dang. It’s something else entirely.
Yeah the initial text makes it sound like an attacker can trick the AI into revealing data from another user's private channel. That's not the case. Instead they can trick the AI into phishing another user such that if the other use falls for the phishing attempt they'll reveal private data to the attacker. It also isn't an "active" phish; it's a phishing reply - you have to hope that the target user will also ask for their private data and fall for the phishing attempt. Edit: and have entered the secret information previously!

I think Slack's AI strategy is pretty crazy given how much trusted data they have, but this seems a lot more tenuous than you might think from the intro & title.
I mean it only takes five sentences for the author to make it clear he has absolutely no idea what he's talking about:

> > Before going any further, I want to make it clear that I am just a civilian piecing together this story from whatever information I can glean from the internet.
That’s not true. Exponentials are everywhere. They can often go for a long time. Even silicon is still going strong if you focus on FLOPS per dollar.

Other examples are cruise ship sizes, US GDP per capita, or Microsoft stock price.

The point really is this: go back in time to some of these things a few decades years ago. You would say: “How is this even possible? This is crazy. This will probably plateau soon. This can’t continue.”

But it did. Cruise ships went from 20, to 100, to 200 and now 365 meters in length.

And the same will probably happen for batteries. People say “ah well this is crazy. It will probably plateau soon”. My point is maybe it won’t. Once these exponentials (starts of s-curves) go, they go. Standing at the bottom of an s-curve and predicting the plateau soon can lead to a massive misprediction. Like the IBM CEO who said there will never be a market for more than 10 computers. He was off by about a billion.
What kind of design choices do you find helpful with using a magnifier like that? It's not something I'd ever considered before, sounds tricky to design for but I'll try to keep it in mind now.
> is what leads me to conclude that the Ruby community is slowing down

That conclusion was apparent awhile ago.

https://trends.stackoverflow.co/?tags=ruby,python,php,typesc...
It’s already the case that many of the people involved in publishing an article are unpaid. Authors and peer reviewers are not paid (indeed authors may have to pay for open access). Editors are sometimes paid. There are professionals employed by the publisher – copy editors, typesetters(?), etc – who are compensated, though it is not clear they are providing that much value.
Thing is, those who like cars and driving don't want autonomous cars; those who only see cars as a way to transport humans and goods should stop pretending they want cars and simply use Uber or Rent-a-Van. Self-driving cars are a solution to a non-existent problem.
> Sure it is, more specifically, it is part of a definition. You want it to be explicitly this or that, but things aren't that simple. Sure, we can put a dictionary definition on it and call it a day, but that isn't very helpful. When I talk about innovation in this context, I roughly mean the ability to think of solutions where no previous examples are directly available.

A letter can part of some alphabet, but it is not itself an alphabet. A word can be part of some dictionary, but it is not itself a dictionary. An anecdote can be part of a dataset, but it is not itself a dataset.

I think the definition you now give seems to be reasonable, but I'd like to compare that with the example to illustrate the problem of vagueness here:

> Give an LLM the documentation of a library/framework it has no training data on and ask it to implement a specific thing based on that documentation.

vs.

> When I talk about innovation in this context, I roughly mean the ability to think of solutions where no previous examples are directly available.

The example you give is the kind of thing that LLMs are really good at: translating one thing into another thing. The original use case of the transformer model was natural language translation, and they can do that well even when there's no explicit map from the input language to the output language, as they learn an intermediate representation for all.

The same applies when the languages are jargon and synthetic: "business plan", "code" and "documentation".

Is that innovation? It meets the example you gave, but does it meet the definition you gave? It depends exactly what you mean by "no *previous* examples": myself, I would say that "documentation" counts as "a previous example".

But the more I think about it, the less that actually feels like innovation. It's in-context learning, which is neat, but it doesn't seem to meet what I'd expect from real innovation — at most it is the corporate (and government) self-congratulation that gets called by the same word.

> Extending the definition of innovation, I am highly doubtful the current generation of LLMs can implement frameworks/libraries based on new principles unless very specifically prompted. In which case you have a human architect behind it all, and I still believe you will end up with code that follows paradigms and structures that are at most "current".

This is a confusing point: that sounds like it's about following a new principle, whereas I would expect "innovation" to involve designing and specifying a new principle, determining its weaknesses through experiment. I believe LLMs are used as part of larger systems to do this, though I have no frame of reference for the quality, and I would accept that "LLM as component of bigger system" is different from "LLM" — a letter can part of some alphabet, but it is not itself an alphabet, etc.
Liftoff, by Eric Berger
How exactly do you replace song's lyrics with your lyrics on this website?
> I can look at a CVE and determine for myself and my organization whether it something we need to care about.

Except it doesn't work like this.

A security scanner will include a CVE. People want no red flags on the security scanner. They don't care what the CVE is, they just want red mark go away.

The attitude to accepting useless crap as a CVE is diluting what an important CVE actually is.
Mythbusting 101: Organic Farming > Conventional Agriculture
https://archive.ph/svjSz
Alizondo is not reputable
> Silicon Valley’s tech bros are having a difficult few weeks.

they need to find a different derogatory slur to refer to tech workers

ideally one that isn't sexist and doesn't erase the contributions of women to industry
Can universities just do a buy-out of Elsevier and wind it down? Surely they really have the upper hand here.
Completely random tidbit of information, in Houston (and only Houston) we call them 'feeder roads.'
Not just you, I expected the same, and was just as surprised to find it opens Google Maps in Chrome as well.
Curation is not access. Curation is editorial, in terms of having a journal issue contain a selection of available new works and not every single thing posted.
I think my previous comment was wrong. Anyway, the point is that the original claim

"if you win the lottery jackpot, then you win less than the average lottery winner"

seems wrong unless the winnings of "the average lottery winner" are defined in a quite unnatural way.

In your example the average lottery winner wins 3/4 of the jackpot. Half the winners take it all, the other half have to split it with someone else.
This is exactly my feeling. Cars have gotten so huge now, erasing the fuel savings and causing the deaths of so many pedestrians and cyclists.

I would like to see the cost to register these behemoths to be commiserate with the actual cost to society.
Taichi: Productive, portable, and performant GPU programming in Python
> 1. The Zoom slider: You can't select the different lenses easily (I'd need to set the zoom slider to exactly 5x to get the zoom lens without digital zoom, which is not that easy) and there is no way to quickly reset it to 1x. I also think the position for this slider would be better at the bottom (where most other camera apps put it)

That's not what the zoom buttons do in Pixel Camera and it doesn't switch at exactly the telephoto magnification zoom value but rather adjusts when it switches based on the available light because the telephoto camera can't handle low light as well. We could add 1x for going back to 1x but you can already easily zoom out to the ultrawide and the telephoto is more complex than people realize. You can see it often doesn't actually switch at the minimum.

> 2. The brightness and zoom slider are rather hard to hit, I maybe have a bit too fat fingers for these? (The brightness slider also does not seem to work in night mode) I also can't see the zoom/brightness values while sliding and the Google Camera App allows for more smoother/finer control.
>
> Same with the little arrow in the top left corner, it always takes like 3-5 hits to open the menu. Never had this issue in the Google Camera App.

You can swipe down for settings and can swipe left/right between modes. The arrow is mostly to imply that you can swipe down. We do plan to change the overall layout and sliders/buttons a bit.

> 3. I need to use the QR Code mode to scan qr codes. I did bind the Google Camera app to double click the power button so I can easily take pictures and scan QR Codes, without the need to tap anything else. But It's definitely a cool feature that the GrapheneOS camera can scan many more Code Types and also that the GrapheneOS Camera removes exif data by default

You can open it via the standard Android QR scan quick setting if you use it a lot.

> 4. The mode slider at the bottom doesn't let me scroll further than one mode, this means I'd need to swipe thrice to get to the QR Code mode from the Video mode (or tap twice) because when in QR Code mode I can't see the Video mode and vice versa

We can consider adjusting changing modes.

> 5. I currently tested it out for writing this comment and my phone definitely got way warmer than when using the Google Camera App. And it used 5% Battery while being active for 7 minutes. EDIT: very weird it did now vanish from the Battery Usage list in the Settings, and in the App Info it also says it did not use any battery since the last full charge (It did before)

It shouldn't consume more power than Pixel Camera. Don't know why that would be the case. It does do things a fair bit differently. CameraX is improving which brings improvements to our app without us having to do much and we implemented some things ourselves like the parallelized image saving in the background.

> 6. I think it does not support the Astrophotgraphy (Tripod) mode for the Night Mode.

We'd need them to add this to the extension API.
I ordered something from walmart.com when the same item became expensive on amazon. The item arrived, a fan, and it was used. Not only that it was dirty to the point it had massive amounts of dust buildup. It had to be in use for months. Sold as new.
I start the return process and was told to drop it off at customer service at any store. Get there and they tell me I can’t return it there. Go home, start the process via website. They tell me the vendor will contact me. Days layer they say it was a new item and I must be wrong. Show them pics and they send me a shipping label.

I wasted so much time with this. Never again. Paying $20 for the one on amazon would have saved me a lot of time, which to me was worth more than the $20.
Do you know how expensive open access publications are? I guarantee that editing, typesetting and curating could easily be performed for fraction of that price (and it's easy to prove it - just check how much Elsevier makes each year!). Also keep in mind that most of editors - which are responsible for curating - are not paid at all... And if you mean "curating" as in providing access to pdfs, then there is arxiv which does just that - for free.
The nice thing about post-production apps like this is, though, that you get to choose when and how to apply them. I couldn't live without ML photography tools for fixing lighting issues when I can't do it in camera.

Sadly, most cameraphones are now just applying ML before handing the data out to the APIs. Getting the raw sensor data from some phones is literally impossible for third party apps now, as I understand it (looking at you Samsung).
GM Lays Off 1k Salaried Software, Service Employees
Calling it brainwashing doesn't appreciate that there are tensions between different cultural norms. And if you want to look at it that way, every country is looking to be the best at brainwashing, and China's no slouch there.
yes, definitely. I find it helpful to think of usability and friction as an inverse square law relation [0]. Small increases in friction (x-axis) cause dramatic drop-off in usability (y-axis) to begin with, then correspondingly less so. Specific user tolerance will vary, but adoption broadly follows a similar path - exponential drop off.

I've never seen any data to back this up in a quantitative sense (though interested if anyone has?). Nevertheless, I've still found it useful as a qualitative rule of thumb in a positive sense: shaving off small edges of friction can have non-linear return in adoption and satisfaction.

[0]: https://en.wikipedia.org/wiki/Inverse-square_law
Does it support Numpy and Pytorch?
https://archive.is/4V9TK
I haven't looked at submarine systems in detail, but my understanding is that the big problem is that an ICBM knows where it's starting, but the submarine travels. So submarines have super-accurate inertial navigation systems on board to determine their position.
'Glory to Hong Kong' protest song may be pulled from online sites, producer says
Anecdote but my dog dreams a lot and sometimes mimics the sounds and motions she makes when we play together. Other times mimics chasing things. Seems like reliving her favorite activities. Might not be intentional but its a form of reflection.
Or run VCV Free with all the modules and run a virtual cable to Cardinal. ;)
How would you securely implement this scheme with SSS?
The point stands though. Warships that served the nation and have actual name recognition have trouble raising funds to stay afloat as museums. Keeping some unheard of commercial vessel afloat as a floating ballroom or whatever seems totally unrealistic.

Incidentally, if you're ever in Philly, check out the USS Olympia. There aren't many ships from that era (late 19th) still around. Really cool ship.
The camera app can choose how this works. GrapheneOS Camera app supports HDR+ and Night mode on Pixels along with having comparable video processing including the HDR+ style merging of data across the low-level frames and EIS. Can use Pixel Camera on GrapheneOS if you want the additional features and the more aggressive HDR+ processing it uses with extra features.
There are still buses that sell tickets :O May I ask where? This has been shut down years ago where I live for the time it takes as you say.
>That's already the case now, since there's no perfectly objective way to decide whether a bug is even security related or not.

Sure, you are right that a line already exists. However, that line basically boils down to "could this bug conceivably affect security". The decision tree is 4 questions long -- very simple.

What I am opposed to is someone else answering "yes, this could conceivably affect security" and deciding on my behalf that I don't need to worry about it. That is a line for me (or someone who knows the organizations infrastructure, risk tolerance, etc.) to draw.
So far Elizondo is the only one talking, and he has a book to sell. The things he says sounds "crankish." Count me as skeptical.
They argue that this is not a problem because the IDE automatically renumbers cell references.

Yes, we definitely need more textual (yes, SPL is textual IMO) languages that cannot be sensibly edited without the official IDE. (I'll make an exception for actually visual programming languages, because we don't have a good interoperable format for those.)
This is the real reason there's an SSO tax. It costs to support SSO, the customers who want SSO should pay for that cost.
do you really think anyone actually cares that my comment started with "The TFA" instead of just TFA? Your comment adds absolutely nothing to the conversation.
So you're confirming that somehow the best publishers somehow manage to provide something of value. The people judging your career are the ones you're complaining about and somehow they're choosing to respect a few publishers.

Instead of just imagining that Elsevier is somehow bad, you might ask yourself why these committees respect their journals so much. What are they doing that's right?
I have been using Chat-GPT has a full time expert and I can unequivocally tell you that its a transformative piece of technology. The technology isn't hyped.
I was lead engineer for a startup. By virtue of being the most flexible in my day-to-day, I ran front line for most of the customer support issues.

SSO issues took exponentially longer than nearly every other support issue and accounted for well over 50% of our support efforts.

We didn’t really feel like there was much we could do about it either. Most of it came down to the fact that the user of our application was not the person also able to setup SSO. The result was a massive game of pass the hot potato until we would get fed up and request a call with our customers IT team.
>Except it doesn't work like this.

You'll have to email my bosses that :)
A better UX is to show a confirmation in place. When you delete a task from the list - show a module in its place with a short message and the undo button. Showing a toast in a completely different part of the screen is hard to notice and hard to interact with as it's removed after a short delay. Also, if you delete more than 1 task quickly, toasts start stacking, and it becomes even less clear which one you want to undo.
I've got bad news about your Gmail...
The current status quo is that forty thousand people die from car crashes in a single year.

I think we need to try to use technology to improve the situation, yes.