skysight-inc/HackerNews huggingface dataset:
Apple phones can definitely be locked.

I have an iPhone that is fully paid off. My company was paying for the monthly fee on AT&T for the last year and a half. When I left the company a month ago I switched the phone to a new personal account with AT&T because it apparently wasn't possible to get the phone on a personal account and switch carriers at the same time.

I then tried to unlock the phone to move to a better carrier. After spending hours on support calls with AT&T thy finally told me that they can't unlock it for two months after a new account is created. I asked why and they said, "it's just our policy." May AT&T rot in hell.
> It’s a MikroTik running RouterOS

https://google.com/search?q=mikrotik+botnet

These things are the absolute scourge of the internet.
Every few years I get an automated email from Wordpress where someone finally fixed a bug I submitted over a decade ago, lol
Yup, iirc i paid $1600 (or maybe $1800? I forget) for a new 3080TI. It hurt. However i'd do it again if/when i need to. Ideally i won't for another few years, but you get me.

Clearly i can afford to do this though. But this isn't just gaming either, i create CG on this machine, digitally sculpt, etc.
PG has reached a status where it's difficult to publish thoughts/blog posts that don't have every minute detail scrutinized.

It's also HackerNews so it's a higher level audience too.
Intelligence and radical economic attitudes
> If you have a 4 line stanza that needs a comment to explain what it's doing then I'd suggest that needs breaking out into a function

I'm mostly in agreement, so I'm going to focus on my disagreement too! ;)

This view is pretty common in the ruby community. So much so that I think they take it too far at times. I sometimes find myself reading a class that could have been a single 24-line method but is instead one method with method calls, each of which calls 0-2 more methods.

This style is good for when I'm trying to quickly understand what that class is supposed to do - I just read the top-level method that looks like:

thing = getThing()
munge { |i| thing[i] }
is_foobar?(thing)

But it's terrible when I need to understand what that function is actually doing - eg to debug it or to find some underlying function call I'm looking for. I have to bounce all over the file to mentally reconstruct a linear sequence of code which could have just been one function with some headers.

Of course, this style is a reaction to impenetrable 500-line functions which are also terrible. I'd definitely prefer many small functions to that! I think it's a matter of judgement and experience to know whether some code is better as small stanzas with comments or small functions.
All the class components people wrote still work and can be maintained. React doesn't overhaul everything like Angular did. You can have function components with hooks and also have your old class components in the same app.
I don't know that I agree with that. I recently had to fix a few bugs because some devs forgot, or simply didn't know, that lifecycles still exist.

We have reached a period of time where junior devs exist that did not cut their teeth on class components and have no idea of what the lifecycles are. They don't know how rendering works so they either throw up useless memoization everywhere or they don't bother to think of it.

The complexity of class components did not vanish. It was only swept under the rug. Take useEffect. It's overloaded to hell and back. It does too much and people continue to struggle with it. Another one, useRef. It's not really for refs, per se. You will end up using it for data other than refs because function instance variables aren't a thing. No one knows when to use useLayoutEffect or useCallback.

The fact of the matter is that it's not class components vs. hooks. It's that React's API sucks. It's always sucked. And it continues to suck.
I'm guessing this is small because it relies on GObject Inspection.

This is a Gnome feature whereby C libraries are accompanied by an XML description of functions and types. The XML description annotates semantics, not only syntax. Like if a function has a pointer parameter, does it have to be malloced, and does the caller free it or the callee? This information is not possible to determine from parsing C header files.

If you can parse the GObject XML, you can then generate FFI bindings (which can be done in Lisp easily without any textual code generation hacks).
This hits close to home for me. I donated once to a friend’s campaign for local office and my personal (Gmail) email (which I don’t share with organizations I donate to) ended up on the Democratic Party mailing list and now I get daily spam with clickbait and outrage-inciting subject lines from every party-registered office holder in the country. You can unsubscribe to as many as you want, every day there’s a new PAC targeting you with their spam.
You should really pivot and start selling that software. Package it up with a nice pretty bow and wrapper and it could be a very lucrative product.
With some ISPs, they will issue a new IP if you change the router's (WAN) MAC address. Might be worth a try next time (crossing fingers you don't need it).
They could fire you, dock your pay or demote you
I'm happily using React as a low-level renderer (using Reagent) - I would welcome splitting this codebase up into a pure DOM-diffing renderer and state/event handling on top.
They already offer download servers for free, and I doubt a credit card fee comes close to 30%. I'm not positive what their reasons for choosing to charge on the app store are, but "they couldn't self host it for cheaper" isn't it.
I know they can be locked, but not if purchased from Apple. Which is why I have always bought phones from Apple since 2008, since I always hated the locking game.

But I assume Google or any other manufacturer would similarly not want their customer to end up with a locked phone, hence my surprise that a phone purchased from google also can end up locked.
Vue is mostly used in China, where there is a preference for Chinese tech.
Not really, and it’s not a problem. Ideas for stories are abundant, the ability to turn them into finished books or scripts is much rarer.
Hooks are a natural progression from class components, class components seem more straightforward with all the willMount beforeMount etc. but they trick you into visualizing your component in different states of mounted/rendered/etc. That goes against what React wants to be at its core, which is totally immutable and pure, it isn't mounted or pre/post-render it looks the same whether it is the first render or the 100th. Ultimately I think the mental model of the component as a pure function is superior to juggling the react lifecycle.
undervolted use because not every processing component needs to be used

very different than a car

but valid questions to ask to whoever you are buying from used
> The new tool becomes massive and bloated and overwhelmed with too many features, configurations, and options.

It is almost as if people are not breaking their problems over the correct dimensions.
AuthN and AuthZ: Security, Compliance, and Other Challenges [video]
Hooks are executed in order as they are defined, isn't that a fundamentally broken design in regards to language spec?

I don't have an opinion, just generally curious because it feels very odd that the order of my functions matter.
Thanks. I'm talking with the team.

Edit: see comment above.
According to the article, the US us by far (very far) the worst offender and yet it is only 6x over the target, not 10. Switzerland, which does not strike me as a country with a low standard of living, is 2.5x over the target. Europe 3x.
The latest update added an official modding API, we'll see what comes out of it.
Ask Ukraine.

https://www.nytimes.com/2022/06/25/us/politics/commandos-rus...

But even as the Biden administration has declared it will not deploy American troops to Ukraine, some C.I.A. personnel have continued to operate in the country secretly, mostly in the capital, Kyiv, directing much of the vast amounts of intelligence the United States is sharing with Ukrainian forces, according to current and former officials.
> UAV's for area defense

Are drones any efficient against rockets?
I wish I could understand the appeal of react and other frameworks but everytime I interact with them I find them so terrible opaque and frustrating. I've built plenty of things with various frameworks including react[1], maintained, been in team-based development doing it, have github projects that use them with thousands of stars but I think they are brain-damaged terrible ways of doing things that shouldn't exist.

I've given it a fair shake and I wish I could change this opinion. I'm trying not to rant so I'll stop here.

I do a cathartic exercise every time this stuff gets to me at a themed twitter account. It's pure vitriol: https://twitter.com/sisnode

[1] oftentimes I see the anti-react argument as "react sucks which is why I use Y framework". I'm saying they are all(?) a toxic trend that leads to terrible products; more complicated, harder to maintain, aggressively encouraging a glossary of programming antipatterns passing it off as elegance.
What you are probably missing is that the subsidy is not a lump sup at the time of purchase. e.g. If you get a phone subsidized by $720 from the MSRP the carrier provides a subsidy of $30 per month for the next 24 months or $20 per month for the next 36 months. If you leave early the credits stop and the remaining balance is due. The problem here is that even after the phone is paid off it remains locked to the operator.
This is amazing! Thank you so much!
They're thinking "how do we get those C++ businesses to stop hiring C++ coders, and start hiring us Rust coders instead".

The original purpose of Rust was to displace C, a laudable goal. But it is failing at that, because C coders are practically defined as people who will never switch to anything. (Any who might have did already.) So now the only hope is to displace C++ instead, and the propaganda machine is trying to paint C++ as equally as unsafe as C, which it manifestly is not, lying if that is what it takes.
Props to marmelab's react-admin, and the ng-admin that preceded it.

If you need CRUD without adopting some "low code" platform and its half dozen containers full of weird databases, react-admin is a fine choice.

I have wondered what svelte-admin would look like.
You bring up another frustration I have with Netflix - their recommendations suck! If you don't know exactly what it is you want to watch you're likely going to spend too much time trying to find something.
Depends on what you are learning for. If it is for a job, then react has the most openings by a large margin and will likely stay like that for a while.
> consumer products live or die on usability

Only consumer products in a competitive market, where the UX is everything. Your toothpaste does not live or die on usability; it's toothpaste. It could be less useable than another toothpaste and you probably would never notice. Maybe you buy it because you're brand-loyal, or it advertised a new completely made-up quality, or it's just on sale. Sometimes the UX is just a minor aspect of the whole, like car mediacenter interfaces. Stuff sold by quasi-monopolies don't compete at all; nobody cancels their Comcast Family TV Package because the TV guide's UX sucks.
Indictments Accuse 44 in Minnesota of $240M Pandemic Aid Fraud
My question is: how does it's GC behave under rapid generation of garbage? Any time there's been a page that was poorly responsive under Firefox, but fine under Chromium, when I profiled firefox was spending most of its time in the GC. I've noticed Vue sites to be the biggest offenders, but it's not just Vue.
More or less horrible things you can do to measure Python performance
It doesn't say why one should use this WebAssembly implementation, and not (for example) the V8-based implementation that comes with Node.js.
Building a WebAssembly Runtime for BBC iPlayer (2021)
Not all i386 in name are real 386. Sometimes they think about i586 or i686 (which is way how to mark generations of CPU).

From provided page:

Processors
All CPUs compatible with the Intel Pentium or later, with Intel-compatible hardware floating point support should work.

So no support for real 386 CPU.
Yes, Stable Diffusion performance will improve the more VRAM you give it. This is generally true of almost every ML model, because ML models are often limited by bandwidth. There is a constant need to shove more data into the accelerator, but PCIe is very slow compared to data in VRAM. If you constantly had to push data over PCIe, your GPU would run at 5% of its max performance, and spend 95% of its time waiting on PCIe transfers. Instead, you load a bunch of data over PCIE at once into VRAM, as much as possible, and then you begin working. So the more VRAM you have, the more data you have "in hand" -- so you can have a bigger batch size for your training iterations, for example. So one of the things various releases of Stable Diffusion have tried to optimize, for example, is VRAM usage, because that's the #1 limiting factor for most people.

Modern GPUs use virtual memory so they can see very large amounts of data and the GPU and OS will work together to page data in and out, like normal RAM. But if you want good performance, you need to work out of VRAM, so you need as much of it as possible, so you aren't paging data in and out. (More specifically to answer your question, yes it will page data from SSD into RAM and then into VRAM; this is because the data must pass through the memory controller in practice on most designs to go over PCIe, but if you are using fancier Tesla/Quadro cards, they can actually do P2P DMA transfers and go directly from SSD -> GPU, but this requires special care and support from all pieces of hardware inbetween.)

Note that in a funny twist of fate, the M1 series from Apple kind of has an advantage here. They use very high-bandwidth LPDDR5X for their designs, and the GPU and CPU share that. Which means that in theory, the Mac Studio for example could have astronomically large amounts of VRAM dedicated to a task like ML. So why not use a Mac? Because the hardware is only good as the software you run it on, and training/tuning ML software on Macs is simply nowhere near as well polished as Linux/Nvidia. That's all it comes down to. And I say "well polished" very liberally; in practice it's all a bit of a hodge-podge nightmare because the job is very hodge-podge...
An excellent book. It's a terrific example of how to think about problem solving.
Don't let your work identity interfere with your personal one; you are not your job/career—don't let it get to you. That said, put in whatever your terms of employment asks of you and negotiate overtime compensation if they're demanding more. You have just as much power as they do in these situations.
> And I'd imagine that most folks who are advocating for Svelte never had to build up a startup before.

>Svelte is a great choice for personal projects, but extremely impractical for a startup.

> What about the hiring pool?

> Svelte for the web client is fine, but now you have to manage a different team for the mobile client.

These are interesting assertions and run contrary to my experience. I work for a successful startup and our front-end team uses Svelte. We've had nothing but success. We run a production-grade mobile app (Cordova) on old low-powered client-provided devices including RF guns (Android 5 to 9) with multiple thousands of concurrent users in stores/logistics warehouses, and a web app running on desktop (Chrome/Firefox/Safari). And, every front-end developer we have (including myself) learned Svelte on-the-job within a few weeks.
I like Kotlin. However, these decisions aren't always simple - and are based on more than the technical merits of the language.

Some years ago, my division at <large company> decreed Scala was the way of the future. All new development was to be done in Scala. We were offered training classes. We formed book clubs. We paired, shared, and opined as we tried really hard to do functional programming correctly. We genuinely tried, and then we gave up. The specific reasons would better suit another post, but it was a grassroots developer-led effort that led us to abandoning Scala.

At this point, we have backend code in NodeJS, Scala, GoLang (this is currently a performance-sensitive one-off), and Java. That's a problem for code reuse, tooling reuse, and general maintenance. If we were to write new components in Kotlin, we would be making the problem worse. At this point in time Java is our safe fallback.

In the future we may try a different language again, but for now there needs to be a really good reason to add to our tech stack. I suspect most new projects will continue to be Java for quite some time, because we're not going to rewrite all the Scala and NodeJS code "just because". It will slowly get replaced as it stops working, or as we find reasons to replace it other than "it's in a language we don't like". Until then, our polyglot set of codebases is too intimidating and devs are going to resist adding another language to it.
> At the high-end, Nvidia is making more powerful cards (HP) with the same fuel efficiency as before.

No, perf/w is still climbing every generation. It'll climb hugely this generation too.

NVIDIA's marketing number is 2x perf at the same wattage as last gen, obviously needs to be validated by third party testing but they're shrinking two nodes at once here, it's a bigger node jump than Pascal was.

People have been primed to react negatively by a couple of twitter rumormongers like kopite7kimi. Yeah 4090 has a high TGP, but it's more like 400W TGP (450W TBP) and not the 800W TGP / 900W TBP that he was shouting from the rooftops about. There is still a huge gain in efficiency here, it's just also a very large (and expensive) chip on top of the higher efficiency.

But people don’t discard their incorrect mental frames when the information used to build them is falsified. Actually they just tend to retrench and dig deeper (“450W is still too much even if it is 2x perf/w!”). Ada is a power hog, “everybody knows it”.

https://videocardz.com/newz/flagship-nvidia-ada-sku-might-fe...

People said they wanted a balls-out big chip on a competitive node, that's exactly what the 4090 is, it's highly efficient and very large, this is much closer to the cutting edge of what the tech can deliver than Samsung 8nm junk or little baby 450mm2 dies. Now people are complaining about the TDP and the cost, even if it's more efficient that's not good enough. Unfortunately the TDP is a matter of physics, thermal density is going up every generation and a big chip on a modern node pulls a lot of power.

There are lower models in the stack too and those will maintain that efficiency benefit. It's a larger-than-pascal node shrink, efficiency is going up a lot here.
AFAIR, a 1980's MIT AI Lab "how to do research" memo, suggested as one way to build things: describe what you'd like to build, and maybe someone else will be inspired to do it, long before you'd have gotten around to it.
My knowledge is very specific to just these cards.

The only 'secret', which isn't a secret, was that I realized that since this is hardware, we know the maximum settings (hash/watt) that should be possible. Therefore, I set the cards to that best setting and then tune down from there. This is the opposite train of thinking than most other miners.

Most people think, let's start low and then tune up from there to make them 'faster'. The cards crash when they can't handle the settings, so it turns out that tuning down is a better way to tune since they stop crashing when they are stable... and thus don't need tuning from there. There are 3 different sets of 'knobs' to tweak, so I had to build an algo to adjust the knobs in the right order to tune things down. I just had the concept of 'current -> next settings'.

Temperature and power fluctuations can make the cards crash too... so by always tuning down, you're always heading towards more stability instead of instability. Since neither of those could be controlled, machines would reboot randomly all the time.

The software I built was a golang daemon that ran on each machine and watched for these crashes and modified the tuning of each card individually. The daemon is pretty cool as it is effectively a task runner. I had different tasks to configure and monitor the machines as well. The machines are all independent, idempotent and self-healing workers. Reliably distributing the software to 20k different workers, is a fun challenge. There are a ton of unit tests, so that helped a lot.

If I have the energy, I may rip out the tasks from the daemon, turn it into a library and open source that. It is kind of a fun project that could be useful for others trying to manage large scale individual workers. Tasks could easily be 'apt install' or monitoring utilities. I even bundled node_exporter into the binary, so that we could monitor the machines with prometheus.
> our company is asking us to work weekends and extra hours

This is the only relevant point, and you can get your answer by asking if you will receive additional compensation for the additional time that you're being asked to put in. Paying you a salary doesn't give them the right to pretend that _all_ of your time belongs to them. If they want more of your time, they need to pay you more. If they say no, then you say okay and either stay and work exactly 40 hours per week until they fire you for "not being a team player" or whatever (for which I believe you would have cause to seek unemployment benefits, but I am not a lawyer); or leave.

Putting more pressure on developers is the _least_ effective thing that management could possibly do. Stress produces cortisol. Too much cortisol results in overall lower cognitive ability. Why would you stress out the people who need to be able to think clearly?
When people don't have the ability to update for very low cost
The symbolism of the zoomed out context is hilariously not any less ominous or threatening. The blue coasts surrounding and squeezing the extremist red middle of America. It was bad optics all around, unless it was intended to intimidate, in which case it put the intended targets on notice. If your strengths don't include psychology, metaphor, symbolism, power politics, etc... maybe don't swim in that pool and definitely don't volunteer yourself as a lifeguard.
I've worked in a few roughly-the-same-size (~50 engineers) web development shops. It's always the same. Doesn't matter if it's React, Angular, Class based components, Functional components with hooks, Just Some HTML, PHP, Rails views, etc.

The frontend just collects the cruft of a product organization changing course very frequently. There are always a dozen half-finished fix-the-world ideas conflicting with each other, half-finished move-to-new-framework initiatives.

I just mean to say that when I hear "it's because React" or "it's because rails views", any other of the infinite variations of this, I kind of just tune out. Some part of your organizations chaos is going to reflect in code, and honestly I'd rather it be in a big ball of frontend than in the data models, infrastructure, etc.
People might view it as giving legitimacy to a process.
A chance for the return of the Safari extension perhaps?
I wonder how much sweat equity on aggregate has been wasted through anti-competitive acquisitions like this. It's got to be a lot of hugely valuable human capital, simply squandered.
Where do you work? Does your company set prices to be nice, or do you set them to maximize profit?
It keeps amazing me how fast things evolve once a technology becomes open source. Stable Diffusion is really a game changer.

One pesky note - Would be adding trust if the landing page had a link to the github repo. https://github.com/divamgupta/diffusionbee-stable-diffusion-...
You could at least require that all phones be automatically unlocked when the phone is paid off or when the contract period expires.

The customer shouldn't have to take any sort of action to remove the lock.