skysight-inc/HackerNews huggingface dataset:
It's still very new and working out the kinks in the concept. I wouldn't expect it to take off in the current state. The videos they've done on Linus Tech Tips (Linus is an investor) keep me optimistic about their prospects.
I think you miss the point. With a lot of code once you've mocked out all the dependencies you're not left with anything to test apart from assert derp == derp.
> Every single useful device on earth that is connected to the internet needs to be updated regularly.

Could you explain me why?

I am not saying that developer should simply make software bug free, I know that this is impossible, I however believe that you could heavily reduce friction point by simply having less code, and reducing the software reliance on the hardware/OS

Monolithic projects like Android prevents it from happening, you have to depend on that huge codebase to run any software, and as every software must follow Android update path, you need to continuously update your hardware
I took all the ones I took so far, why stop now?
Poe's law strikes again.

> Until Apple did it, it was not on anyone's minds.

This is too on the nose.
Yeah if you want to kill yourself from frustrations, maybe. I'm not writing microcontroller code for the fucking space shuttle, and I would suspect most people aren't.

C did a ton of things right, but it also did a ton of things wrong. Learning from that and moving on would be the sensible thing to do after 50 years.
Is there like a cash prize for solving a major problem with one of Google products? It seems disingenuous for Google to frame this as some academic challenge when it's clearly for Bard, Google's commercial product.
A good PM can add a lot of value, but without a team, they're useless. You may know how much revenue your product generated for the company, but do you know how much of that revenue you generated yourself? In my experience, it gets nebulous very quickly.
I’ve been annoyed they can’t provide any updates. How hard is it to provide a few sentence update every week like they do with the 16
It is! I did meet him, it was really cool!
Fortunately there are a number of KIM-1 replicas for someone wanting to play with an early 8-bit computer but either don't want to pay the high price for an original or don't want to end up worrying about restoration of an artifact like this guy, ha ha.

I have built two replicas now, the most recent was the PAL-1 [1] kit. I also built one from Briel Computers some time ago but his business appears to have disappeared.

The nice thing about the KIM-1 replicas/clones, as opposed to some of the Arduino or Raspberry Pi based ... emulators? .., is of course the real 6502 chip as the CPU.

Also nice about the KIM-1 in general is that the six 7-segment LED displays give you both the address and data at that address at once (and in hexadecimal). Other early 8-bit machines of course displayed data in binary (via das blinkenlights).

(Another clone that looked to be outstanding was made by Corsham Technologies. Sadly the man behind the clone died just a month ago and so those machines have also stopped production.)

[1] https://www.tindie.com/products/tkoak/pal-1-a-mos-6502-power...

[2] https://www.corshamtech.com/product/kim-clone/
Side-note: I really hate the “Prefer x” formulation. Write “I prefer”, as in almost every case, you’re expressing your own opinion
I'm with you for a smaller phone. A Sony Xperia X Compact with no bezel would be great https://gsmarena.com/sony_xperia_x_compact-8292.php

And the lightness!
So does it mean it's not possible to have popular apps like whatsapp or Tinder on this?

I also wish it was just a phone with much less performance for a smaller price.

I want something durable and repairable, not something fast, Wirth's law is very important to consider when consider software and hardware. I hope they will make such phone, one day, because I am not spending that much money for a phone.

I bought a 150 euro phone and it already lasted 3 years, because even if a phone becomes obsolete, it is still cheaper, per year, to use crappy phones, than to use a durable expensive phone.

If your really care about fairness and the environment, make lightweight hardware and software.
To add to that last point, after some time being frustrated with an FP4 and browsing the FP forums: it's not just availability of spare parts to repair shops. There doesn't appear to be a single mention in the forums of a repair shop willing to work on the FP4. There are numerous mentions of repair shops that are unwilling to, and of people being unable to find repair shops. Warranty repair is actually outsourced to a generic warranty support company that appears to operate on standard, replace-everything basis.

Apparently, for the FP4 (reportedly in a departure from some previous devices), all software development is also outsourced. Security patches are often months out of date. Known defects with basic functionality (camera hardware should be fine, but is almost unusable for many tasks because of poor firmware/software making, eg, focusing ridiculously slow; microphone noise and echo reduction has serious problems for calls, etc) go unaddressed, or, in worse cases, are acknowledged as something that won't be fixed, especially for the bizarre security flaw that the manufacturer's official OS is signed by test keys, and the device is set to trust test keys, something that apparently can't be changed, and makes the device one minor leak away from having secure boot entirely broken. This is apparently one of the reasons why GrapheneOS developers refuse to consider supporting it. At the same time, other flaws in the security design make it very easy to brick the device, as you point out, and FP charges for unbricking (the test key problem apparently makes it unsafe for them to release a fix): in one case on the forum, a user bricked the device by correctly following FP's own official instructions for updating the OS manually, and FP refused to unbrick it without charge.

I was astonishingly disappointed by the FP4, to be honest, and by Fairphone in general.
You are right. I was thinking of distros in the same league as Fedora or Ubuntu. Debian, Suse, RHEL all play nice with Secure Boot. Of the big ones only Arch does not work with Secure Boot out of the box.

I guess many minor distributions don't bother at all. Thanks for pointing it out.
I’d say it’s an alternative to Instagram, but not Flickr. A huge distinguishing feature of Flickr is that it keeps high-quality versions of uploaded photos. Instagram and Pixelfed compress to a low quality. Pixelfed’s UI also suggests that it’s more of an Instagram replacement, i.e. more about the social media aspect than about the photos. The photos are just an excuse to do social media.
Yes I may be an idiot, though this has worked well at several places.

For example, this worked really well for us at Shopifys Discovery team at for moving fast on search relevance and recommendation systems. To clarify how to build and test search experiments really fast. I would say it’s the default model/culture at Shopify.

(Not away team per-se but more the “OS” model)
Public libraries were invented a long, long time ago. These days, the internet is even better than the public libraries used to be.
companies do not, and at times cannot, simply hire and fire as inefficiencies are noticed. it is a process, and often a poor one.

the employer keeps paying them, so the larger system evidently tolerates their current efforts. for the time being. this is not the same as their amount of work being about right.

unless you intend to say that milking a system without hitting the breaking point is optimal.
For most users, it only takes one critical app to say it refuses to run because the device is too old, and the user will upgrade.
I fully understand your concerns, but still I believe that you aren't asking yourself the right question. Why do you need to port newer Android versions on older devices at all? It seems like the real problem to me.

Why do running newer software must depend on a newer operating system? Do you believe that everything that is part of the android codebase is necessary to run a chat app?

Part of the problem is that we seemingly gave up on trying to make software stable, and now we are wrongly putting the blame on hardware manufacturers for not wanting to spend their whole life supporting it
> The problem stemmed from differences between European and US payment systems, which meant that when certain transactions were declined Revolut would erroneously refund accounts, handing them its own money [...] In late 2021, organised criminal groups took advantage of the fault, encouraging individuals to try to make expensive purchases that would go on to be declined. This would then be cashed out via ATMs.

$20m seems like a lot to lose without internal controls flagging anything. The issue was only discovered by a US partner bank that informed them about their lower than normal account balances.

BDO did not provide them with a clean audit, pointing to revenue recognition and internal controls issues [0]

[0] https://www.reuters.com/business/finance/revoluts-2022-reven...
Formatting is not the only component of code style, it's just the part that can easily be automated. Anytime there is more than one way to do something, and both options are correct and produce the same result, the choice between them is likely to be a matter of taste or style. For example, using a loop instead of using a map function. You can automate some of that stuff, but never all of it.
But isn't a dotnet runtime a feature? AOT strips a main feature of the language, while still doesn't even get close to compiled languages ( hello world < 300kb (or < 100 kb compressed))
You make some good points here.

1. I stated index in this post (whoops); luckily I called it a list on the website.

2. Partly, in seeking an income strategy, that seemed important to me. Also, frankly, it allowed me to limit the scope of my dataset a bit. Maybe I should go back to the drawing board and include quarterly stocks as well, though.

3. I'll look into it

I'll jump ahead and answer your last question as it's relevant to the others: I'm using Polygon.io's API to pull financial data. I too have noticed that the data can be unreliable, repeats, and has many records missing certain data. I've sanitized that data on my backend, checking for and removing duplicates, as well as only displaying historical records with adequate data. Beyond that, I'm not sure how to improve the quality.

4. What about dividend reinvesting? Can't you avoid taxes if you do that?

5. Is that also true with leveraged funds? It seems like many of these high yield dividend stocks are in that category.

6. Interesting, I'll look into that.

Hope I responded to all of these points adequately. I appreciate the thoughtful and intelligent answer. I'm still not sure (and need to do more research) on whether such a dividend strategy is useless. It seems like reinvesting could provide good returns as a strategy--when the stock dips, so long as the payout is constant, you simply get more income. Maybe I'm missing something, though.
You say the experiment has failed, but speak purely of theory. The actual experiment, the one running in practice, is an astounding success; the things you describe happening don't happen, or at least don't happen in Rust.

In practice, a dependency I should not trust to have done diligence in semver management is only a couple steps past a dependency I should not trust to run on my machine. Ignore any dependency with less than 50k downloads and 'what if other people are dumb' concerns like this one just melt away.
I would suggest picking some valley and coating it with polysiloxane (silicone).
More thoughts about this, inspired by the ongoing talk https://dev.to/smonff/notes-about-the-ongoing-perl-logo-disc...
I'm not sure that it's truly all down to software, but as far as it is, you don't have start at zero -- there are excellent, competitive raw photo processors available as free software, like darktable and RawTherapee. Still a lot of work, though, no doubt.
There is no reason to think a ground-up rewrite of existing working code will lead to better and more maintainable code.

As with almost every argument in this area that depends very much on context.

A substantial rewrite might be an opportunity to use better tools and improved techniques that have been developed since the original was written. In some cases that could represent a huge improvement in things we actually care about like developer productivity and the quality and performance of the product. Importantly this doesn't imply anything was done wrong or any bad decisions were made by the developers of the original product or the people who have maintained it so far. It's just that we work in a fast-moving industry and sometimes even a few years can see some big improvements in what the available technologies can do.

A development team starting with a relatively clean slate can take into account all the knowledge and feedback received over the lifetime of the existing system. Maybe it was too expensive to make use of those insights while evolving the original system but a new version can take advantage of them. Again that can represent big gains in areas that we care about.

It's often observed that a big rewrite risks losing a lot of small improvements and fixes that have accumulated over the lifetime of the existing system and of course that's true. However it's also true that a big rewrite can avoid a lot of existing design problems or get rid of long-standing bugs that no-one was ever going to get around to fixing.

I've seen big rewrites that didn't end well. But I've also seen big rewrites that were done for sensible reasons and had very positive outcomes. And I've also seen things that should have been rewritten but weren't and instead became a drag on everything. There is no universal rule here.
>well, you may do that, but it doesn't make it so. the linker has much less information to go on than the compiler - basically (depending on how you compiled) machine code. actually, the GNU linker does quite a good job, given what it has to work with.

but it was their decision to split the tools like that, wasn't it?

nothing technically prevents you to model it in such a way that you can have access to the data you need, right?

You probably don't even need to have linker at all.

>> Other language (compilers) do better.

>a language is not a compiler

I wrote compiler in parenthesis.

Also, since "language" has two definitions

1. syntax

2. whole ecosystem

Then it is valid either way
Leslie Groves:Oversaw the Construction of The Pentagon and the Manhattan Project
You can’t, but no one can do that really unless you are the inventor of a product that didn’t exist and had no prior competing already products in the market.

The point of all of this is the following: If I am a key component of a team company product that generates $100 a year in revenue my value is dramatically different to the organization than the person who is a minor player in a team product that brings $1B in revenue. My value is very high within my own product, but my product’s value is not very high to the organization. Understanding my impact on company revenue can tell me “am I safe in this role?” Or “I need to find another role because my little project is ripe for plucking”.
It is indeed not possible if we keep making software the same way. But it doesn't have to be.
> USB-C port getting dust

The designers of USB-C should be ashamed of themselves for not doing more durability testing. Both cables and sockets are big pain points for most users.
Author here! Excited to see this on the front page, ping me with any questions!

I recently gave a talk about the tool, addressing:

- why semver in Rust is important and harder than it looks

- how the tool works

- why it took until 2022-2023 to solve this problem

There's no recording but here are the slides: https://docs.google.com/presentation/d/1gVYM9-YLrBmRYSuHqW8r...

A lot of semver is just queries over APIs. For example: "find public functions that existed in the last version but don't exist in the new one." Any such function we find is a breaking change.

Cargo-semver-checks uses an engine designed to query any data sources called Trustfall, and uses rustdoc JSON (which has an unstable format that changes ~once a month).

Here's a query playground where you can try running queries over rustdoc:

https://play.predr.ag/rustdoc

More info about all this on my blog:

https://predr.ag/blog
> I think this can be frustrating for more mathematically-inclined people, who want to be able to test the function not just for a couple examples, but for the entire domain of inputs, which then leads to a lot of interesting but less pragmatic fancy ideas approaching formal verification.

I am that person! I am a big fan of property based testing and try to add such tests whenever possible. They serve as "edge-case hunters" and are usually part of my programming loop. As soon as something has been modified, a test suite executes. Writing property tests first and the code later allows you think about the invariants and behaviour of what you are building in a way that regular unit tests just don't.
What Is the Python Global Interpreter Lock (GIL)? (2019)
Reading this and your other comments I have two very conflicting vibes that I:

1. Hard disagree on the idea of multiple styles in a single codebase and think being able to identify writers of code by style rather than version control sounds like madness incarnate.

2. Massively want to read a blog post or something from you about your ideas on code style. Sounds like you have some pretty valid and well thought out ideas justying a philosophy of code style I've never heard supported before (I think normally disparate code styles in a code base would get interpreted as a code smell rather than a positive)
It looks like many of the high yield dividend stocks are leveraged funds. Does the same rule hold true in that arena? The historical data on those stocks doesn't seem to support that on first glance, at least.
Lego Ideas: Working Lego Bicycle
Doesn't that mean that buying the newest Fairphone in 2023 gets you 0 years of Android updates and 3 years of security updates? Compared to 4 years of each with a midrange Galaxy A?
> It shouldn't be a patch release and it's not supposed to be a breaking change.

Such change is not distinguishable from a patch release because, according to the semantic versioning, both should be trivial to upgrade. In the other words, if the semantic versioning did work as intended, upgrading from 1.2.3 to 1.2.99 and to 1.42.0 should be same to users. If it's not the case, there should have been some breaking change. And clearly this is not how users feel about the minor version increment.

> Outside of new things it informs you about the work expected with downgrades. Going down in minor versions and you should check for breaking changes or removed functionality.

If you need downgrades the distinction among major, minor and patch versions does not matter because either:

1. The library author has broken the premise of semantic versioning, or

2. You have entirely separate requirements that are not part of the public API (whatever it is) and thus the library author didn't honor them.
Clean functions with limited dependencies which encode non-trivial domain logic are indeed well served by unit tests - even if theyre a bit imperative.

But, outside of contrived interview scenarios this type of code is actually somewhat niche and outside of that niche unit tests suck.

Ive worked on tons of projects where it accounted for 1-2% of the code base. Unit tests not only werent capable of catching bugs they werent even capable of replicating 98% of them. Unit test theater.

Meanwhile, the other day I did TDD with hermetic end to end tests using playwright, mitmproxy, mailpit and screenshot/snapshot testing. It felt like I was living in the future.
> Billionaires are both, and more: mortal gods who embody our aspirations of success, plenitude, and security

which billionaire paid for this?
Hmm, maybe I'm misunderstanding, but AFAICS I am able to paste file paths into those dialogs? Steps to reproduce: copy a file path, Ctrl+O, Ctrl+L, Ctrl+V. So I guess I'm misunderstanding what behaviour you're referring to?
Clockwork Orange did much better https://www.rottentomatoes.com/m/a_forbidden_orange
Google will no longer let you upload an app to the store that is compatible with old android.

Doing so is a privacy loophole, since newer OS's have stronger privacy protections.
Are you old enough to remember Lindows? in like 2000/2001 it was a straight Windows ripoff, even used the old Win 9x/2k theme iirc, and had WINE built in, preconfigured and would intercept windows programs automatically and run them via that. It was blatant enough MS actually took them to court, ended up settling by buying the Lindows trademark from them for 20 million and getting a pinky promise they wouldn't be so confusing to consumers by trying to pass it off as a Windows equivalent. The product was eventually renamed Linspire and continued as a noob-friendly distro with less 'Hey, we're actually Windows!'.
Trace Explorer
C has no in-built way to deal with SIMD, which is essential for high-performance computing over loads of data. On that count alone it is already out of the game.
More reasons:

Phone is lost

Phone breaks beyond a reasonable cost of repair

Phone fills up with WhatsApp pictures and after months or years of deleting them they buy a new phone with double storage, which is already not enough.

Children grow, get the old phone of one of their parents and the parent buys a new one.
Thanks for the feedback, this is exactly the sort of info I've been lacking, not being an expert in the space myself (only a journeyman, if that). I'll check this out.
To be more specific, 23andMe shows your full exome which is where proteins are encoded in your DNA. Sort of like how having the entire codebase doesn't necessarily tell you what's going on in production with memory corruption, behavior on certain hardware, cache misses, etc. the analogy works well.
It's simply not possible to make bug-free software that's supposed to interact with the internet.

And even if it did, it would take so long to develop that it would never get released before it was already too old to be useful.
* Easily damaged by moisture (even though they've claimed certain IP ratings), due to the printed conductor inside the plastic layers with pin connectors

* Battery swelling after less than two years of operation (no way to source this battery locally since they've built a custom connector / redesigned an standard OEM battery)

* Overheating

* Touch screen glitches (they've resolved that after a year via software, support was super unhelpful with that problem)

* Wi-Fi 5 GHz broken/unreliable for many people

* Camera focus (not sure if FP3+ improved on that front)

* Broken fingerprint sensor (from the beginning, most common issue) and by broken I mean not functional at all

* self-disintegrating plastic parts (back and side covers), likely due to the fact they are using recycled plastic - they've changed the plastic chemistry with FP3+, for me the plastic became more and more brittle

-

In addition for me with software:

* charging LED can't be disabled, which is extremely bright when you're sleeping - community members shrugging this off with "you shouldn't use your phone in your bedroom anyway"

* screen brightness too bright / unreliable brightness sensor readings (they had several updates because it was so hard to tweak for them)

On the positive end:

Phone is quite durable, fell down on many occasions and because of it's plastic/design openness the battery falls out but screen never broke in bunch of occasions.

Edit: Formatting
Is this an article written by AI linking to another article written by AI?