skysight-inc/HackerNews huggingface dataset:
If the OS supports it, you can make programs that start threads on CPUs and GPUs and let those communicate. You run the SIMD-ish functions on the GPUs and the non-SIMD-heavy functions on the CPU cores.

I have a strong suspicion GPUs aren't as bad at general-purpose stuff as we perceive and we underutilize them because it's inconvenient to shuttle data over an architectural wall that's not really there in iGPUs.

Maybe it doesn't make sense, but it'd be worth looking into just to know where the borders of the problem lie.
I have never worked in PT jobs, but as a contractor based in Mexico, I usually apply for remote positions on LinkedIn, particularly in SAP Commerce development.
Someone needs to explain to me how a primordial black hole in a neutron star doesn't implode into a full black hole in seconds.

Correct me if I'm wrong but a neutron star is basically a huge atomic nucleus. How would any primordial bh not immediately start sucking on mass at extreme speed?

Is it because the event horizon is that small?

Anyway I would think the persistent survival of neutron stars would basically invalidate the existence of swarms of black holes.

Neutron stars are some form of superfluidity. Do black holes lose momentum if they suck in matter moving more slowly than them? They must. So some high speed primordial black hole would slow down and suck in matter rapidly.

You'd think the hole would suck in mass until the point the neuron star partially unbinds.
> SSR for frameworks is an absurdly complex solution to a problem that doesn't exist if you can just send a complete document right to the browser.

So, React is just a view library. It's made to map state to DOM changes. Except it's not just a view library, because if you write an app with React, you are writing a React app. You slice and dice your view up and put them into React components. Now, since you want to use your React components on the server and not slice and dice them up again in another view library, you morph that DOM-manipulating lib into a templating engine that generates static HTML. Except you call it "server side rendering", because "templating engine" sounds so 2010 and "static site generation" is also not the right term, because the output isn't a static HTML page, but can change with every page request. Of course, the "React" part of React is completely ditched in SSR, because you don't need to continuously modify the DOM based on your state. React on the server is what PHP templates have been doing forever. Outputting HTML in PHP is "view = f(state)". We've come full circle.

I sometimes wonder if younger web devs even understand that SSR isn't, like, really rendering a page on the server, but basically means "we produce frickin HTML like we've been for the last 30 years, except our tools are now 10x as complex to such a point that we don't understand them anymore", because 90% of our view library does nothing on the server, because, you know, there is no DOM. There is only HTML as a string send over HTTP.

Having said that: Your analysis is completely correct. The discussion really is orthogonal and I'm not sure I see the point in rendering web components on the server, since most web components benefit from interactivity through JS. If I merely encapsulate a bunch of HTML tags, I can ditch the custom element entirely and send the HTML tags down the wire by themselves.
So what's the best solution? Suppose you have a dumb TV, or a smart TV locked to a single input. It seems like there are big downsides to most approaches. Rokus and Fire sticks have the same downsides as smart tvs, with ads and laggy interfaces. I currently have one output from my desktop hooked to my TV, but the UI leaves a lot to be desired and of course now I have two input devices to deal with, one for the TV and one for the PC. What's the best way to do it?
From the story, I couldn't suss out much mission detail.

A wiki shares some of the stuff the unit did back then.

https://en.wikipedia.org/wiki/480th_Intelligence,_Surveillan...
If b is negative, define c = -b, and use the linked result to show that

a^2 - b^2 = a^2 - (-c)^2 = a^2 - c^2 = (a + c)(a - c) = (a + b)(a - b)
Design docs are much easier to be reviewed. Throwaway code/a prototype is a huge amount of content where it's easy to miss things.

When I go back to understand a component, I want to know why the decisions were made. A well written doc illustrates exactly that - here are the options considered, here is why we chose this option to be implemented. It can be quickly read and searched.

Throwaway code - even a pull request with comments - is not the same. It takes much longer to process, much longer to review, and it's easy to miss seemingly obvious things because the important bits are surrounded by a bunch of unimportant boilerplate.

Put another way: anything that could be represented by a single PR is generally not significant enough to need a design document. Anything significant enough to need a design document should be a chain of smaller PRs / commits which allow the pieces to be reviewed thoroughly by themselves and have tests to show that they each work.
Which is cheaper? A change in code? Or a change on paper?
The thing that strikes me is the disparity in length. I think a lot of people don’t realize how hard it is to write succinctly. Jobs was (is?) probably under-appreciated as a writer.

Colligan was correct such an agreement would be illegal and could have just stood on that.
There’s no need for this extension: https://news.ycombinator.com/item?id=42425681
There be tumbleweeds, but if you automate/habitize these and don't expext too much should be OK. Even full time jobs are this hard to get RN!
What scares me about the need to recompile statically linked binaries is that the problem is invisible until a bug hits. You don't know the statically linked library is vulnerable unless you keep track of all versions that went into that binary and almost no organization does that.

DLL problems are very easy to see and very obvious when they happen. But it's been a long while since I last saw one.
If you don't mind paying more, they do exist in the form of digital signage / commercial displays. They're usually either completely dumb or support "smart" features via standardized pluggable modules, which can host a normal x86 computer, amongst other options.
Lightbulb after lightbulb going off in this thread :)

As the person who posted about the option to lock selected apps - notes and voice recorder can be easily excluded from that set.
Honestly, I am open to any Linux-related opportunity that comes my way: that number has been 0 lol
Nice, I will check your solution too. I would also love to have NotebookLM available via API, it could be nice to generate podcast-like guides.
My workaround is to use a computer monitor connected to a Linux box that I actually control.
LinkedIn Guide for Engineers and Managers
Is it really programming if you can't do pointer arithmetic and poke memory addresses? I suppose so but you're not really programming for a machine you're playing in some language developer's bubble-wrapped sandbox.
I use an HDMI switch and it works fine for me.
Ask HN: What do you think about creating video captcha?
Hi,
Taking into account current state of AI and the fact that it is harder and harder for ordinary captchas to really distinguish between bot and human I was thinking about idea of creating video captchas were people will need to use camera and show something on camera to prove that they are real humans. What do you think about such idea?

Best, Wiktor
1) It will probably not be "consistent", so you need to ask for more pay than you require, so you can last through the droughts.

2) Your best opportunities are places you've already worked, because they know you and you know at least some of their infrastructure, code base, etc.

3) Very small companies are more likely to need a generalist, and be unable to pay for a full-time on-staff person. You will need to let a lot of small companies know what you can do, and spend a lot of hours doing that, which no one will pay you for.
> Ideally, I would get 10-15/hr a week retainers, but project-based work is ok too. The key is that I can keep getting the work with consistency.

Work like this is more commonly described as freelance, consulting, or contracting.

If a job is advertised as "part-time" they're usually expecting you to work every single one of those hours, unlike a retainer where you're expected to be available for up to that many hours.

It may sound pedantic but it's important to understand the difference when searching for roles. If you take a "part-time" job they're generally going to want you to be working for every one of those hours, even if you have to find your own work to do. If you treat it like a retainer job where you're only expected to be on-call if they need you, you could run into some disappointment.

Using the right terms will also help you find roles that more correctly match your expectations.

True part-time work is hard to find because most companies would rather hire someone to work 4 x 40 hour weeks on a project instead over the part timer who wants to do it in 8 x 20 hour weeks or 16 x 10 hour weeks.

This leaves work that is sporadic and spread out, or companies that have a need but can't fit full-time compensation into the budget right now. That's a hint for the type of work and companies you'll need to seek out. Trying to pitch yourself as a valuable contractor who needs 3-4X longer to finish a project due to your short workweek isn't a winning strategy for most jobs.
Get a short throw projector. You can plug anything into it. It’s the perfect “dumb” screen.
I don't like that description very much. The cell being "alive" is literally the top reason the cellular machineries work so well. By being "alive" it is keeping the environment optimal and perfect for the enzymes to run and being productive. Taking this away and then seeing problems about efficiency is like taking off the wheels and then asking why the car is not running well.

They are trying to fix it by maintaining the same cytoplasmic conditions using all the machines and sensors in a bioreactor. But that can scale is a different question. The narrow ranges of conditions biological processes require is already hard to maintain while the cells itself is still whole and using more than half of its enzymes to do this.
WRT 2:

I do indeed think that it's mostly about effort vs. reward, and that sufficiently low cost of energy, and sufficient time resources, would solve it. But the cost of energy would have to be near zero, and the time allotted would have to be very generous. This is because most mic/webcam/etc. data is of very poor quality -- probably poor enough to actually poison datasets -- so it would need to be mercilessly cleaned up, and then laboriously chunked and sorted. When all's said and done, you're going to devote tremendous labor to cutting >99% of your data, and more labor in categorizing it.

It might be more fruitful to develop a model that creates new training data from internet-derived data. This is a lot more complicated than it may sound, and I don't think I ought to speculate here as to what might be involved, but it still seems more viable than sorting through a low-quality material library of babel.
Wouldn't that be pretty good value add? A mic feeding data to some AI model and then camera to track how many people use it or stop and watch.
I feel like it is the same form of intellectual stimulation that one gets from crosswords or sudoku but with an added creative dimension. Where crosswords and sudoku present a challenge with a fixed target goal, the demo scene and virtual consoles give you the difficulty with an open ended goal.

Code golf is somewhere in the middle, Often you have a fixed goal, but there is no one 'right' solution, creativity can find many paths to achieve the desired output while reducing line or character count.

So I do

Dweets https://beta.dwitter.net/u/lerc/top

My own fantasy console https://k8.fingswotidun.com/static/ide/?gist=ad96329670965dc...

A stack machine image generator limited to 50 characters of program code https://c50.fingswotidun.com/

Why do it? Why play with Lego? It's interesting and you get to see what you make.

The proliferation of fantasy consoles is simply because making a fantasy console appeals to the same aesthetic. See what you can make.
> WCs are standardised and will continue to work basically indefinitely regardless of the ebbs and flows of popular libraries

Help me understand; is this suggesting that older frameworks/libraries are expected to stop working at some point? I'm shipping 10+ year old libraries in production without incident. Really don't understand the "resilience" argument for WCs.
I bought my 65" TV for $299 recently, including shipping to my doorstep. Clearly all the bullshit that's baked into it is subsidizing the price by a lot.

I just never gave it network access and I use it like a dumb TV with a streaming box, so I get to benefit from a price subsidized by the the other 98% of the population who are getting exploited. The whole thing is kinda gross.

It's like there's this enshittification tipping point that you can't come back from. Realistically, who is going to buy a dumb TV at a much higher cost? People who are already savvy enough to get around a smart TV? People who aren't? I don't see it working.
I would totally buy it.
I use a short throw projector with an Apple TV. There’s also a little device called Micca which you can use to play video files you’ve downloaded.
I bought it because it did not require a subscription and because it sounded like a smallish business - told me I had to wait a few days for it to be 3D printed.

I love the simplicity of it, the fact that it’s driven by fulfilling a need and not by greed.

Not affiliated in any way. Wish I had given this to myself years ago.

Also wish I had come up with the idea myself.
Is there a central repository where all these tech emails are coming from or are they discovery from disparate court cases?
IMO GP is about the labelling: Instead of a2-b2 use longer2-shorter2 (and on visual representation one side will always be longer, as per GPs explanation).

Diagram doesn't show proof for "shorter2-longer2". I believe showing negative area would spark more controversy (imagine that negative area is painted orange, visual area would still be positive).

Shorter2-longer2 gives you same absolute value with reverse signed, so it feels symmetric to me (can't remember what the formal definition is), i.e:

1. a2 - b2 = ( a-b)(a+b) # * -1
2. -(-a2 + b2) = -(-a+b)(a+b)
3. -(b2 - a2) = -( b-a)(b+a) # / -1
4. b2 - a2 = ( b-a)(b+a)

Edit: https://imgur.com/a/olETWfr - crude image with labels swap as it seems it's bringing some controversy.
It's not binary. Valid uses of a technology don't mean there aren't others using that same technology in a resume-driven manner.
Raspberry Pi 500
> For chatbots, 99% is amazing in terms of utility.

Is it really though? If it's 99% of generated tokens, then 1 out of 100 being wrong is not great for code generation since you're often going to generate more than that. But let's suppose it's 1 in 100 whole functions or programs that's wrong. Unless there's a way to automatically verify when a function is wrong the error rate basically makes full automation, e.g. automatically fixing GitHub issues, out of the question.

So it seems like at 99% we're left with a system that requires constant vigilance from the user to check it's work. This is a far cry from the promise of true program synthesis.

What would be amazingly useful is a 99% reliable system that can tell you when it can't answer the question correctly instead of providing a wrong answer.
The NY Times isn't a left wing rag (I'm excluding the Opinion section, which is a very mixed bag). It's the mouthpiece of the establishment.
a business owner being 55+ is different statistic from a founder being 55+
Y Combinator's 2024 year in review
> The only true random sources in the universe are quantum. But it's not practical or performant to hook your workload up to a raw quantum measurement like the spin of a fundamental particle, or radioactive decay.

I was under the impression that's how entropy generators for servers work?
Just turn off the privacy invading features. LG’s options are pretty great, I’ve seen little bloat, and get the native apps for streaming services just fine.
If fully invested in just the S&P 500 with 10x leverage, it seems less mathematically possible to have lost just 52% unless it was an very short time horizon. If fully invested, A 5.2% decrease in the value of the S&P 500, with 10x leverage, would lead to a 52% fund draw down, given no margin call during the 5.2% S&P draw down. In most years, the S&P experiences at least one short-term draw down off the years peak of at least 10%, which would lead to a complete loss of capital, given that they hadn't already experienced a forced liquidation due to a margin call on the previously 10x levered assets, which would now be levered higher given a loss in the capital base.
That is very valid subtext but I also believe Stephen King was wigging out detoxing from booze and blow with his family in CO and remember some Bradbury he read. Both can be true. King was so good he doesn't remember writing Cujo like Bowie doesn't remember recording Station to Station

Eyes Wide Shut is visually captivating string theory goodness - you can lose your mind over the rainbow right quick - but also I think Arthur Schnitzler wanted a little taste of that hot secret pre-WWI Vienna action that he'd never get (I'm all about that fallacy of authorial intent).
Yes, I used to feel the same.

Until I did some research and found out there is no need to go to this extreme --- at least not yet.

It is possible to buy a "smart" TV at a price subsidized by the privacy of "dumb" users and still run it in a "dumb" display mode.

With the TV I just bought, this is called "store" mode. I use it as a big, dumb 4K display connected to "smarts" that I can control.
Both statements are true. As a baseline it's good to consider the price of the regular TV's before they got smart.
> LLama 3.2 Vision 8B

Brainfart, that should of course be LLama 3.2 Vision 11B. Keep mixing up the model sizes.
Just don’t connect it to wifi, connect an Apple TV or similar to hdmi 1, and move on.

I’d love a dumb TV, but if you don’t let them online and don’t use built in software it is close enough.
Good point yes. That explains why he's getting performance similar to the leading frameworks. Those tensor operations are helpful for training or for throughput-optimised batched inference but not really for a batch size of one.
Two can play at that game:

"I declare myself the victor!"

Wow that is very easy, maybe that's why it's so popular.
I don't think they need any of your prayers, they're likely better than all of us combined and better than any person who joined Apple later.
They are different court cases, usually popularized by techemails (https://www.techemails.com/)
I worry about how long it'll be before the manufacturers either make the TV demand an internet connection, or simply build one right into it.
Here is some material to challenge that idea:

https://danluu.com/productivity-velocity/

Is also funny to phrase it in terms of bottlenecks because bottleneck optimization is an 80/20 approach to performance. People who are serious about perf don’t practice it.

80/20 is good for once a month tasks. When it comes to the primary work I do everyday I don’t want to leave 20% on the table.
It's the morning, and there is no coffee and there is no way to get coffee
what about laptops? can we connect them to the internet? tablets? phones? :)
This has clearly been heavily edited by humans.
I think it’s easy to forget the palm pre and webos because it wasn’t a competitor for very long, but to be blunt, it was the only decent competitor to the iPhone but in the 2008/2009 timeframe. Android was awful on launch, blackberry was completely behind, Microsoft had a plan that was decent but was too late. Palm really was the only real threat in the early days. They just didn’t have the money to iterate like apple (and Google).
Regulation can prevent the fix as well.
It think it mainly depends on the difficulty of the problem.

If you're working on a very difficult math problem - say, a novel proof - you're definitely going to lay out the tools and techniques, the various steps of the proof, before you sit down and start writing it out. But for homework problem #7 of 14, just start doing it - you'll figure it out.

Similarly, if you're writing a CRUD app in a stack you've used before, you can probably just start. But if you're writing something complicated that you haven't done before, you should probably visit the whiteboard before the IDE.
> Family controls are pretty good nowadays, fwiw.

Yeah, I do feel like people confuse "giving children their own smartphone" with "giving children unrestricted access to a smartphone". Parental controls really change the equation.

And counterintuitively, giving children their own smartphone actually reduces risks, simply because you can enable family control on it.

I'm not a parent myself, but as an uncle, I recently had to diagnose an android phone which had started popping up random ads. The diagnosis: parents will lend kids their smartphone, kids will install random free apps from play store, which are malicious. And Google provides absolutely no way to prevent kids from installing free apps, short of family control (there is a setting that prevents kids buying apps without a passcode). And you can't really put family control on your own phone, the concept of family control (and apple's parental controls) is designed around giving kids their own smartphone, and using the parent's smartphone to manage those restriction.
It's almost like there an agenda to allow for corporate and government control of all technology.
I'm a big fan of prototyping to explore a problem space. I think some initial design sketches are useful, but you often reach a point where you can only learn by implementing. I've encountered so many design constraints in the past that I couldn't have planned for, but perhaps others are better at comprehensively thinking through a problem space than I can.

I agree with the blog post that doing a hacky solution is very helpful to understand the problem space better, although I think it's something that's challenging in an organization. In a lot of orgs, it might be viewed as a waste of time to work on something hacky. It could also come across as wasting people's time by engaging in too many discussions over PRs. People want shipping solutions today, not explorations that might need to be rewritten later. Asking for feedback might also come across as someone being unsure of a solution and needing "help" on it.

The dynamics of working in a team generally nudge devs to make more conservative moves and writing more up-front design docs, which will be slower and safer. I'm not arguing that's a bad thing, though. You need the documentation to communicate intent across an org and many other people will need to pick up the work, too. A PR may not provide enough space to comprehensively explain the overall design.

As an indie dev now, I find sketching some designs, followed by prototyping, then "massaging" the prototype into a working, shippable solution the ideal workflow. However, it only works because I'm solo and don't need to worry about getting an okay on potentially risky solutions or having to communicate and get buy-in on implementations. In a company that has lots of other devs and lots of paying customers, I wouldn't be able to do things that way, and for good reason.
compare Olin Shivers: https://scsh.net/docu/html/man.html
Mainly Russian, Ukrainian, Philippino, Syrian, Lebanese.

imo schengen doesn't matter for Cyprus. On the contrary it will make Cyprus even more attractive to financial refugees who will use it's geographic location as a stepping stone to the rest of EU. That means a lot more cost for the government to house people until their refugee status applications are processed.
macOS 15.2 Brings More Audio Bug Fixes