skysight-inc/HackerNews huggingface dataset:
>I have a PinePhone, with the distro that was recently selected as the "official" one, so it's supposed to be the most polished[1].

It isn't. It's only pre-installed because there's a money deal involved with pre-installing it. Manjaro also did weird things like announcing they have working MMS when they didn't, and even outside of phones are considered to be a weird distro given their relationship with Arch. Going by the IRC channel, a lot of people install a different distro.

>I can't even do things as basic as placing an app icon on the home screen, and expect that it will still be there after the next reboot.

Known plamo bug that they haven't fixed in forever. I stopped using it for that and other reasons and have no idea why people like it. phosh works fine.

Also, "things as basic as" implies that saving the positions of homescreen items is somehow more fundamental than everything else on the phone, and if they can't get this to work then obviously everything else must also be broken. It isn't, and it's not.

>So it is not a daily driver by any stretch of the immagination, regardless of what you mean by daily driver.

It makes and receives calls, sends and receives SMS, downloads voicemails, runs an up-to-date web brower, takes decent photographs of documents when a scanner isn't available, and allows me to ssh to my other machines.

Turns out different people have different criteria for their daily driver phones. Shocking.

>Even if your idea of daily driver is "a feature phone would do", it's still not there yet (MMS not being fully working, most feature phones have that).

a) MMS matters to a few select countries in the world. But since you assumed everyone else has the same view as you about what a daily driver is, presumably you also assumed that everyone else finds MMS important.

b) Dumbphones can't do three of the five things I listed above as my criteria for a daily driver.

c) In the US, it's next to impossible to find a dumbphone that will continue to work in the next few years because of carriers shutting down everything that isn't 4G and 5G.

Really, all this conversation thread has revealed is that people don't think there's a middle ground between a phone that's 100% usable by all 8 billion people in the world and a phone that's 100% useless.
I personally prefer keybase but to each their own. UX matters to most people and there is no obvious solution here that I could recommend to people that are less technically savvy than the typical HN commenter.
So get into the specifics of every instance. Trust me, the world is bored, we’ll be judge and jury on this.

Don’t be half assed about it. Ya’ll wanna air it out, air it out.
Have you tried SqlAlchemy? I liked that it felt a lot more like writing sql, whereas Django feels like trying to force a different model on top.
https://github.com/embarkstudios/rust-gpu would be the closest equivalent, AFAICT.
Effect of Biocyclic Humus Soil on Yield and Quality Parameters of Tomato
Sure it does, just not one centralized one. LLVM and GCC are very actively maintained and both main teams have many active C++ committee members. Unless you want to split hairs and argue semantics, they are the closest thing to a day-to-day development team and are quite underappreciated if you ask me.
I've never used Google as a domain registrar. They're evil enough for other reasons that I wouldn't feel comfortable doing that.
Work at small startups to accelerate your growth then once confident start your own.
You should take a few days off. If you are in the US, there is a holiday coming up. It doesn't appear that they have anything pressing for you to work on. Take a day or two off for yourself, and then start looking for another job.
Ok checked more...

With #define _AIR_MEM_SCOPE_DEVICE 0x2 and:

typedef enum __air_mem_flags {
mem_flags_global = 0x1,
mem_flags_local = 0x2,
mem_flags_texture = 0x4
} __air_mem_flags;

and

__attribute__((__no_duplicate__)) void _air_llvm_mem_barrier(__air_mem_flags flags, int scope) __asm("air.mem_barrier");

what does _air_llvm_mem_barrier((__air_mem_flags)mem_flags_global, _AIR_MEM_SCOPE_DEVICE) result in for you?

Some things in that make me go hmmmmm though, will ask Apple for some answers.
I knew someone who was working for a post-Kodak spinoff (Alaris). They tried just that-- to reframe themselves as a company that managed memories. It was an interesting concept, but I think they came in far too late in a crowded space.

https://www.kodakmoments.com/
While waiting at the bus stop (in north eastern large city) today I overheard a guy tell his friend his catalytic converter was stolen for the second time.
> that implied portrayal of "wife sits at home goofing off all day because machines do all the real work" couldn't be the norm.

The history of women's work is a history of unpaid labor. The reality maintenance machinery supporting this is powerful. From devaluing industries which see a change in gender participation, to not classifying certain tasks as labor, the mechanisms of maintenance range from insidious to ridiculous. Understanding what happens if that reality is not maintained is important to understanding why it is maintained.
I wonder if it could perform much better than 1/8 of the 3090 on memory bound applications, given that its 400GB/s bandwidth is 1/2.34 that of the 3090's 936 GB/s...
"Fast", to me, from a software development perspective can still be meaningful, in the sense of knowing what techniques, patterns, paths, ... enable performant execution, and providing easy and straightforward paths for the user along those.
Which, ultimately, leads to high performance in most ways the user will apply the provided framework (in a more general sense of the word).
Hope that makes sense.

And it must be OK to claim "fast" as a goal, from the early stages of a project, even before it may be possible to create any meaningful benchmarks. As long as it's discernable for the intended audience the precise stage of development or maturity the project is currently at. Which, I believe, the project in question is communicating just fine ("still in early development").
I realize that the positioning of the ErgoDox thumb clusters aren't for everyone (I only use the two big keys), but I use the thumb keys a lot. In combination with QMK, my thumbs work a lot harder, but I feel it is much more efficient. This design lacks the "thumb power".
Turns out asshole can make good software!

It's almost as though software development skills aren't correlated with social skills...
Are coin collectors really annnoyed at bitcoin using the word "coin", like you have personal knowledge that this is a common thing coin collectors are annoyed about? Or you're just hypothesizing it for the sake of argument?
My 2 cents: if you have a good relationship with your manager and you think they are a good manager I’d stay, but I’d tell them that I’m stressed with the situation and feel that we’ve lost a lot of the know how while I’m still new - they should understand and support you, and defend you if criticism comes in. I’d also do my best to increase knowledge to fill the gap and angle for seniority - it’s actually (probably) a net win in your situation unless the current state is a shambles.

Of course it might not be the current great resignation behind this, I’d also try to figure out if something else is going on.. is there a culture problem, is the manager no good etc..
You might already know this but anything labelled as grade A cells on Alibaba is a scam pure and simple (especially at 100$/kwh). You will get a grade B (used) cell with a somewhat diminished capacity that won't hold for 10k cycles.

To be clear those are usually still great value, but it's worth nothing because people are generally unaware and don't understand that discrepancy between Alibaba prices and what you'd get from a supplier in the US.
Twitter Suspended Me for Saying Rittenhouse Did Nothing Wrong After Acquittal
The performance is terrible.
anything written by balajis can be safely ignored. guy's a loon.
it's not illegal to loot Walgreens unless you aren't wearing a face covering
Anecdotal:
I right away, broke my screen
** from my perspective **
dropped something on the screen,
the next time I used it there were all sorts
of horizontal and vertical lines on it.

My wife got me a replacement because that is how she is.

I contacted the company to see if there was anything I could to try and fix the old one ...
I am not opposed to opening it up an poking around.

They suggested I send them pictures of the damage
then replied that it should not have happened
and exchanged with a replacement.

Noting that at no point did I ask them for anything
and took full responsibility (in writing) for the
impact I assume caused the failure.

I have nothing but high praise for their "support".
Misogynist is a little anachronistic here, given this was the societal norm.
The first sentence is false - unless we cannot find anyone who both likes functional languages and does not like NixOS... Which is quite easy to do. Then you say the only reason they could state for not liking it is the "hacky implementation" and bad documentation. Sure...
I can't speak for the person you're replying to, but some people adhere to a consequentialist worldview, where intent does not matter (or matters relatively little). It's the same outlook that creates the need for good Samaritan laws. I don't agree with it in whole form, but it should be recognized as a valid philosophical framework.
That hasn't been my experience. (Sample size one).

I also use the Norman layout on my ErgoDox, but Qwerty on normal keyboards. Hasn't really been an issue (other than learning Norman).
is crypto currency intentionally hidden or obscured?
G. PlayStation doesn't do Vulkan

H. Switch main API is NVN
I could use a new technical book to read. Is this the one you're referring to? https://www.amazon.com/exec/obidos/ASIN/0471197130/thean04c-...
From a quick grep, it looks like this wrapper does not automatically call autorelease, so autorelease happens only when a method implementation autoreleases its own return value (or if you call autorelease yourself).

Objective-C has a standard rule for when a method is supposed to autorelease its return value: to quote the metal-cpp readme, it's when "you create an object with a method that does not begin with `alloc`, `new`, `copy`, or `mutableCopy`". In many cases, these are convenience methods that also have equivalent "initWith" methods, e.g.

[NSString stringWithFormat:@"%d", 42]

is equivalent to

[[[NSString alloc] initWithFormat:@"%d", 42] autorelease]

But I'm not too familiar with Metal, and… it looks like Metal doesn't have very many of these methods in the first place. Instead it has a lot of 'new' methods, which shouldn't use autorelease.

When a method does call autorelease, Swift doesn't have any way of getting around it, though if there are autoreleasing and alloc/init variants of the same method, it will prefer alloc/init. Other than that, Swift likes to use the function objc_retainAutoreleasedReturnValue [1], which may prevent the object from going on the autorelease pool (with the 'optimized return' magic), but only as a non-guaranteed optimization.

[1] https://github.com/apple-opensource/objc4/blob/a367941bce42b...
But there is relative to plain rust. Besides, even if nobody is trying to write slow GPU code, it's a very easy thing to get subtly wrong resulting in 10's of % speed loss.
PETAL (Phoenix, Elixir, Tailwind, Alpine.js, LiveView)
More Effective Agile
I second NextJS, you get React, SSR, serverless endpoints and a rich ecosystem of integrations. It works great with things like Friebase, Supabase or any regular DB / Redis.
Where I live dropped mask mandate only to bring it back in a few months with a strict vaccine mandate.
Do you have any source to back up your first claim? My understanding is that general anesthetic has been fairly well understood for some time and relatively free of long-term side-effects.
Go to grad school, live as a Ph.D. grad student; then, once you earn that, stay as a postdoc. Never leave.
C++ Mascot
https://github.com/RDambrosio016/Rust-CUDA/blob/master/guide...

* Missing Atomics -- Gamebreaker IMO. Atomics are absolutely essential when you are dealing with 10,000+ threads on a regular basis. You'll inevitably come across a shared data-structure that requires write-access from each thread, and some coordination mechanism is needed for that. Atomics are one important fit.

Ironic, a few days ago, I argued for the use of Fork-join parallelism in most cases (aka: Kernel launch / synchronized kernel exits). Now I find myself arguing the opposite now that we have a topic here with missing atomics. Like... atomics need to be used very, very rarely, but those rare uses are incredibly important.

* Warp Vote / Match / Reduce / Shuffle missing (Very useful tools for highly-optimized code, but you can write slower code that does the same thing through __shared__ memory just fine)

------

Wait, does this support __shared__ memory at all? Raw access to memory is not really amenable to Rust's programming style, but its absolutely necessary for high-performance GPU programming.

If this is missing __shared__ memory concepts, then the entire idea of "efficient GPU code" is dead IMO. GPU threads can only communicate quickly over __shared__ memory within an OpenCL Workgroup / CUDA Block (A Workgroup or Block is roughly a grouping of 1024 "threads" or SIMD-lanes)

All other forms of communication are incredibly slow. Atomics are maybe the next fastest form of communication, but only across __shared__ memory. Relaxed Atomics to global memory are reasonably performant but once you have either Seq-cst or Acquire/Release semantics (aka: the right memory barriers in the right place), things slow down dramatically in GPU-land.

The big issue is that __shared__ memory is only 64kB in size, its locked down to workgroups / blocks. In NVidia GPUs, the __shared__ memory "eats" into your L1 cache as well (In fact: __shared__ memory can be thought of as programmer-managed cache. The caching heuristics just aren't good enough for high-performance GPU programmers. They want to manually manage that high-speed memory for maximum performance).
Does the second quote apply to "reading HN"?
"anything related to energy that has a climate impact should not be measured in dollars, but in co2 equivalent..."

It depends on what you're trying to do with the data. If you're trying to estimate the economic competitiveness, then $ is absolutely the metric more likely to in fact be a predictor of that. For example, will renewables continue to get market share, or is that in danger of being held back by battery cost? If battery cost is falling exponentially, we're in good shape. If battery cost is _not_ falling exponentially, then it could be that we need to explore alternative ways to store the energy. Whether or not $ _should_ be the driving factor, the reality is that it _is_ the better predictor of market uptake.
I have a kinesis edge for the same reason.
> intended to falsely undermine your reputation

I did not know that insults are capable of doing that. If the insult is based on something accurate, then what is wrong with it? Just realize it is based on reality and improve. If it is not accurate, then why give a damn?
I developed software for lottery and casino services, and when I read stories like this the first thing that comes to my mind is this "golden ticket winner" effect that ranking algorithms are designed to generate.

The chances of winning the lottery are so low, but whoever wins will get so much media coverage that everybody believes they can win.

I don't think it's a coincidence that "poor" content makers are on top of the transparency list, it's just the algorithm exploiting this "you can be a winner too" effect.
Beyond Metcalfe’s Law for Network Effects, and Towards a Better Model
It absolutely is the best. Ray Porter’s way of narration opened a new, almost visual, dimension. Maybe it’s this very intimate „inner speech“ style, but to me this was a truly novel experience.
Hmmm...I see you've never had menudo or haggis :-)

(Yes, I know tripe is not really stomach.)
XDA Basics: How to unzip files on Android through third-party apps
Flask.

Very lightweight without much black box magic.

Miguel Grinberg’s tutorials and book are a great and quick crash course.
I'm sorry, this is complete nonsense.

Something you recently Googled is your knowledge, for the time being. It is not external.

You may have an inflated sense of being able to retain it going forward, but that doesn't make it external.

It's no different from any kind of learning.

If you're able to recite the information without looking at an online reference it's internal, and if you looked at it a month ago, it's even long-term memory. It might vaporize in another few months, but that doesn't mean it had been merely external.
I don't think it's related to that.

It's been many years, but even on Tiger I seem to remember it shipped with an old OpenGL version. I can't find the actual version anywhere though.

Here's a post on Google Groups from 2006 stating that Tiger didn't have full support of 2.0:

https://groups.google.com/g/comp.graphics.api.opengl/c/AXFx1...

OpenGl 2.0 was released in 2004.
What about offerings geared to enterprises like Docusign or to smaller enterprises? Are there no technical barriers at all? What's the bare minimum to be a digital signatory to a document? Obviously it varies by jurisdiction to jurisdiction....
I know what you mean. I solved the issue with a specially designed adjustable linkage on the Lagrange (https://github.com/dpapavas/lagrange-keyboard). It took a while to finetune the relative position anf attitude (which, turned out to be what one'd expect: 0° toe, separation at about shoulder width), but now it's finally consistently aligned every time. (The palm keys also help by doubling as guides to keep your hands in the right place.)
Well, as the saying goes...it takes one to know one ;-)
The parts when he troubleshoots are the most educational by far. He explains the theory, he puts it in practice, and debugs the result. Also, his editing is perfect IMO, he really knows how to teach.
With COVID rife, and too few people vaccinated, the outcome of "people also need to move on, and live freely" is spread, mutation, infection, and many many deaths - both from COVID directly, and also from people with other conditions who can't get optimal treatment due to hospitals and especially ICUs being (literally) full of COVID sufferers.

That's what restrictions and lockdowns are largely driven by: preventing disasters within the hospital system.

So... how do you weigh up loss of human life on a massive scale, against "living freely"?
Global Rivalries Are Miring the Clean Energy Revolution
The reMarkable is one of those devices for which I consistently feel like "I'll wait for the next one".

Few reasons why:

- backlight

- ocr

- better pen and eraser

In my mind I'd like to make it a "programming sketchbook", where every time I save, text get OCRd, compiled and I get some compile information out of it.

Obviously I would be just sending the buffer to an external computer and get the output, or something like that.

But the current reMarkable and its ecosystem made me think what I was looking for was way too experimental.
PHP and jquery.
Sex Ed, One Instagram Post at a Time
‘I can’t do this any more’: US faces nurse shortage from burnout
And if free software existed for any of those chips, FSF would require it. If there is any room for consistency in the criteria, it would be to deal with the fact that some of the computers have less nonfree firmware than others. Eg: the raptor computer has far less than the x200.
How would this compare with Accel (which is also built on the cuda ecosystem)?
Not sure why you were downvoted for this.

Considering that some of the magic in these things is the shared, local memory with a very wide bus it would seem obvious that trying to go multi chip would indeed be a massive headache in this regard
Japan’s curiously quiescent inflation rate
yup. boggles my mind how one person can simultaneously understand that the aggression trumps non-aggression AND put their faith into "crypto-civizilation". any cryptography, regardless of how advanced it is, is utterly powerless in the face of simple techniques like thermorectal cryptoanalysis :-)
I looked at the flutter gallery and it looks like they just compile everything to js files and paint the widgets on a canvas element. Would be interesting to know if they're investing any effort in different backends like WASM. Would probably solve their performance problems. Canvas is obviously a sensible option for rendering but it looks like it might be another reason why their performance isn't great.
I think it's hard to say there isn't demand since it was so ridiculously expensive prior to SpaceX. Getting things into orbit at this price point is quite a new thing. In a recent post on this blog, he talked about how before SpaceX, even basic things headed into orbit had to be redesigned entirely to satisfy grueling mass requirements. I wouldn't be surprised if it takes a few more years for people to realize that they're not subject to those restrictions anymore and to fully understand the import of that. (Indeed, the prior post I mentioned is called "Starship is Still Not Understood.)
An “incident” with the James Webb Space Telescope has occurred
Huh, I'm surprised. I had just assumed without looking that this library provided wrapper classes where the copy constructor calls retain and the destructor calls release. Apparently not.
Adding to what others have said, lines of code isn't a great measure of the quality of a project. There's beauty and elegance in simplicity, and creating something well-structured and concise can take incredible skill. In fact, Svelte is also such a project; I believe version 1 was under 2000 LoC

One more thing, software is more than just the code. Documentation is also a critical component of successful and useful software, and the submission does an amazing job of making this approachable and useful through Rich's characteristically clear documentation
Interesting that Svelte hasn't come up yet. Personally I find it to be the only sane web framework out there. Easy to learn, little boilerplate code, very well structured, very fast. Give it a try!
All three.

Start looking for a new position. Things could go well, but if they start going badly, you want to have options outside the company.

Start fishing for new opportunities within the company. If you're not also leaving, there must be something there worth keeping. So, if it looks like you're not on a project that is good for you, another project could be a better hole for the you-shaped peg.

Start talking to your manager. If they haven't cancelled the project yet, maybe there's something going on behind the scenes. If you're going to be the senior employee on the project, you should have the pay, title, and fancy business cards to match.

But do all three concurrently. There's no reason to let any one of those interfere with the others.
> I might suggest...

Best way to suggest is with a pull request.
Can't speak to that specific complaint, but Gandi has had other issues in the past.[0]

[0] https://news.ycombinator.com/item?id=22001822
> it's likely in a professional setting, isn't it?

Not necessarily!

> usually have to go out of your way to cross them in a professional software development environment

I believe this subthread is about the situation of some example hypothetical person being a user of a project in which there are "bad" things going on (whether or not there is a CoC in place that is being violated).

This user is not the one perpetrating abuse.

Say that user reports some problem and is treated abusively or whatever. Or just learns about that kind of thing going on in the project, and disagrees with it.

So question is, why would that user continue to use such a project.

Well, there is the answer: people depend on stuff in ways that they just can't drop it because of someone's behavior.
I'm going to start calling ETH non-fungible (it is fungible but you can't afford to)