Hacker Newsnew | past | comments | ask | show | jobs | submit | raffraffraff's commentslogin

> Creating a viable alternative to Visa and Mastercard requires “several billion euros” in investment, according to EPI’s own estimates. Low interchange fees under EU regulation make profitability difficult.

I think it's absolutely amazing that "crypto" (from bitcoins to shitcoins) have turned out to be no more useful as a currency than chips from the local casino. This has damaged their ability to function as a simple currency that can be used to pay for goods and services. And they have damaged the reputation of the whole distributed ledger technology to the point where, in 2026, banks aren't even considering implementing a closed circuit inter-bank distributed ledger as a way to send euro from one bank account to another. If the digital currency in this closed system was actual euro, there would be no reason to speculate on its value and turn the whole thing into a circus.

I'm sure I'm missing something (a lot actually)


How the hell is it possible that they're still using the ATI domain and HTTP 2026? They acquired ATI 20 fucking years ago.

It really makes you wonder what level of dysfunction is actually possible inside a company. 30k employees and they can't get one of them to hook up certbot, and add an 's' to the software.


Their own people too

I don't know why these aren't used more in building fabric. There's a youtuber who makes these phase change solutions out of various salt mixes aiming for the correct change temperature for a specific application. Eg he made panels for his shed roof (keeps it cooler in sun, warmer at night). Obviously this works better to smooth out large, reliable daily temperature swings, and offers little to someone in a constantly hot or constantly cold place.

I live in Ireland where night/day temperature swings are small. To cool my attic on a hot summer day I'd need to move that heat into a large water tank that gets used for laundry, cleaning, showers etc and is refilled from cold mains water. But fitting an air to water heat exchanger inside my attic would be a big expense and I would have to make sure I didn't freeze the attic.

Regular air to water heat pump could be hooked into my existing tank I suppose?


The name of the YT channel is NightHawkInLight[0] btw. Absolutely worth checking out. He creates materials with extremely useful properties from household materials (eg. PCM (high heat capacity), highly reflective paintings, Aerocrete (high insulation/fire resistance), ...)

[0]: https://youtube.com/@Nighthawkinlight


So if you had a pension mostly in all world indexed funds, you'd switch them over to "boring" investments like cash.

The next stage in all of this shit is to turn what you have into a service. What's the phrase? I don't want to talk to the monkey, I want to talk to the organ grinder. So when you kick things off it should be a tough interview with the manager and program manager. Once they're on board and know what you want, they start cracking. Then they just call you in to give demos and updates. Lol


There is the code, the recorded state of the infra when you applied the code and the actual state at some point in the future (which may have drifted) . You store the code in git, the recorded state (which contains unique IDs, ARNs etc) in a bucket and you read the "actual state" next time you run a plan, and you detect drift.

These days people store the state in terraform cloud or spaceliftor env0 or whatever. Doesn't have to be the same infra you deployed.

If you were a lunatic you could not use a state backend and just let it create state files in the terraform code directory, check the file into git with all those secrets and unique ids etc.


Shanling OS is trash. Absolute trash. Hiby OS is decent.


For me it's not arbitrary. An android device is a general purpose handheld touchscreen computer that happens to be used for music. That means a bunch of things to me:

1. "Touchscreen first" UX

2. Heavier than it needs to be

3. Worse battery life compared to a non-Android device

Using a touchscreen in the rain is impossible. Running out of battery sucks. Going for a run with a 240g brick is no fun, it'll pull your pants down to your knees and trip you.

Compare the specs:

    Hiby R1
    Dimensions: 86.9 x 60.6 x 14.5 mm
    Weight: 118g
    OS: HibyOS
    Battery: 19 hour play time
    Price: $159.00

    Hiby R4
    Dimensions: 129.6 x 68.3 x 18.5 mm
    Weight: 231g
    OS: Android 12
    Battery: 11 hour play time
    Price: $249
These are the things matter to me, in addition to the UX, sound quality, Bluetooth support, expandable / removable storage and sane file-based playlists.


> For me it's not arbitrary. An android device is a general purpose handheld touchscreen computer that happens to be used for music

Android is just an operating system. I’ve developed and shipped Android based devices that have no screen at all.

Android and Linux are both used for a wide variety of embedded systems. Saying they’re all general purpose computing devices isn’t true.

> Going for a run with a 240g brick is no fun, it'll pull your pants down to your knees and trip you.

Then don’t pick the largest device with a big screen? There are many smaller DAPs and phones that run Android. The reason that device is so large isn’t because it runs Android.


Generally, across most DAP manufacturers, the android devices are all of those things that I don't want, and the non-android devices tend to be cheaper, lighter, with better battery life. I don't specifically choose non-android, I specifically chose those other parameters and have simply noticed a pattern. I don't doubt you, but you haven't given any examples and I'm not going to spend my life searching for the exception that proves the rule.


My first Android phone was a Samsung Galaxy S2. It weighted two grams less than that Hiby R1. Of course it was much larger, but tiny by today's standards.

https://m.gsmarena.com/samsung_i9100_galaxy_s_ii-3621.php


Never mind mp3 players, I'd love a small phone again also. It's ridiculous that there isn't a single decent android phone


I loved the buttons on the Galaxy Spica https://www.gsmarena.com/samsung_i5700_galaxy_spica-pictures...

Now that I think about it, going no-buttons might have been a driver towards larger screens. Having at least a few buttons seemed to make it much less necessary.


> 240g brick pantsing you

Sometimes I wish people from 1995 could read our threads and see the things we’re complaining about.


240 grams is twice as heavy as for example an average minidisc player (https://www.minidisc.wiki/equipment/sony/portable/mz-g750) which could often weigh less than 100g.

The very first cassette Walkman was about 40 grams light: https://www.soundandvision.com/content/flashback-1979-sony-s...

The Rio MP3 player was 109 grams: https://arstechnica.com/gadgets/2016/10/diamond-rio-pmp300-m...

The classic Creative Nomad weighs in at 45g including battery: https://www.crutchfield.com/S-HglCxgxN2we/p_053NX128/Creativ...


> 240 grams is twice as heavy as for example an average minidisc player (https://www.minidisc.wiki/equipment/sony/portable/mz-g750) which could often weigh less than 100g.

The parent comment chose an unusually large DAP with a big screen to compare to. It’s not really a fair comparison.

Also the weights of old devices are usually listed without batteries, which could increase the overall weight by 50% or more.

I had a minidisc player a long time ago. It was a quality one, but it wasn’t the lightest or more robust thing to carry around.


You see that I used the weights including batteries for all but the minidisc player which is specced at 144g including those, right?


Almost certainly a typo, the first Walkman was 390g or 14 ounces (not 1.4oz)


Yes, it seems you are correct. For example this one is 180g including batteries: https://www.1001hifi.info/2025/01/sony-wm-20-1983-worlds-sma...

Though I stand by my implied argument that older devices were not as heavy as we might remember them to be. And it is okay to consider 240g a bit too heavy in the context of a digital music player with no need for cassettes or mechanical parts.


I read the advert as claiming that the headphones for that Walkman are 1.4oz, which seems plausible (they're a very flimsy design).


Well, I had something like this back in the late 90s (can't recall the year exactly)

https://walkman.land/aiwa/hs-px297

    Battery: 1AA gets 30h
    Dimensions: 111.4 x 29.1 x 80.7 mm
    Weight: 132g
Ok, so you were limited to 90 minute tapes with slow seek. But aside from that compare it to the specs I posted for the android vs non-android mp3 players. Remember, this cassette player has some seriously impressive clockwork inside that case and it's still smaller and much lighter than the android.

Also remember you can just buy another AA battery, and keep a few spares in your bag.


Ok, and each AA battery you keep in your bag adds another 23 grams, so "a few" (let's say 3) and you're already right back up to 192 grams


If you're going running with your Walkman I think 30 hours on a single AA would be fine


We live in 2026 now, with expectations that are matched to the current year.


I've got the Hiby R1 and have been pretty pleased with it. The R1 doesn't actually run android but just straight linux. It boots up in about 6-8 seconds and returns to the place you previously were. As for physical controls it's got easy to identify buttons for volume, pause (double click for previous track) and next track that are pretty easy to find in a pocket.

No experience with the R4 but seems to have good reviews with the hifi crowd.


Whats wrong with some Nokia brick? Has bluetooth, probably 3.5mm jack too, lasts a week, has more physical buttons than you need for playing mp3s. Costs little


I have a few, and for managing and playing music the UX is absolute ass. Fine for dialing a number and occasionally switching to silent mode, but that's about it.


Does the battery actually last a week while playing music over Bluetooth?


They last so long you forget they need charging.


You can write an agent.md file and gradually add to it as you develop the project. The reason junior developers get better is that the context goes from low to high over the time you spend working with them. Yes, "learning".

I've found that maintaining a file that is designed to increase the LLM's awareness of how I want to approach problems, how I build / test / ship code etc, leads to the LLM making fewer annoying assumptions.

Almost all of the annoying assumptions that the LLM makes are "ok, but not how I want it done". I've gotten into the habit of keeping track of these in a file. Like the 10 commandments for LLMs. Now, whenever I'm starting a new context I drop in an agent.md and tell it to read that before starting. Fella like watching Trinity learn how to fly a helicopter before getting into it.

It's still not perfect, but I'm doing waaaay more work now to get annoyed by the LLM's inability to "automatically learn" without my help.


There's limits to AGENTS.md too, a junior will start to understand the concepts/rationale and design decisions and be able to apply that knowledge to future problems, the LLM will not.

It's way too literally in its thinking.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: