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

In the context of determining responsive layout:

> Using characters as the unit of measure ensures that we get the right behavior no matter which device you’re using and in a number of other scenarios such as multitasking on iPad or even if you simply enlarge the font size past a certain point.

Nice idea! I haven't seen this before.


I think what the author was alluding to was the path integral formulation [of quantum mechanics] which was advanced in large part by Feynman.

It's not that finding closed form solutions is what matters (I don't think most path integrals would have closed form solutions), but that the integration is done over the space of functions, not over Euclidian space (or a manifold in Euclidian space, etc...)


> two versions of the same phone with different processors

That's hilarious, which phone is this?


Basically every Galaxy phone comes in two versions. One with Exynos and one with Snapdragon. It's regional though. US always gets the Snapdragon phones while Europe and mostly Asia gets the Exynos version.

My understanding is that the Exynos is inferior in a lot of ways, but also cheaper.


In the past using Snapdragon CPUs for the U.S. made sense due to Qualcomm having much better support for the CDMA frequencies needed by Verizon. Probably no longer relevant since the 5G transition though.


Not one phone, they did this all over the place. Their flagship line did this starting with the Galaxy S7 all the way up to Galaxy S24. Only the most recent Galaxy S25 is Qualcomm Snapdragon only, supposedly because their own Exynos couldn't hit volume production fast enough.


"Galaxy S II" and its aesthetics was already a mere branding shared across at least four different phones with different SoCs, before counting in sub-variants that share same SoCs. This isn't unique to Samsung, nor is it a new phenomenon, just how consumer products are made and sold.

1: https://en.wikipedia.org/wiki/Samsung_Galaxy_S_II


The S23 too was Snapdragon only, allegedly to let the Exynos team catch some breath and come up with something competitive for the following generation. Which they partly did, as the Exynos S24 is almost on par with its Snapdragon brother. A bit worse on photo and gaming performance, a bit better in web browsing, from the benchmarks I remember.


The S23 was also Snapdragon-only as far as I know[1]. The S24 had the dual chips again, while as you say S25 is Qualcomm only once more.

[1]: https://www.androidauthority.com/samsung-exynos-versus-snapd...


This is the case as recent as of S24, phones can come with exynos or snapdragon, with exynos usually featuring worse performance and battery life


I might be out of date, but last I knew, it was "most of them."

International models tended to use Samsung's Exynos processors, while the ones for the North American market used Snapdragons or whatever.


Several high end Galaxy S's AFAIK.


I don't understand the point? You can say that about anything, and that's the whole reason why it's good that alternatives exist.

The clear target of this project is a k8s-like experience for people who are already familiar with Docker and docker compose but don't want to spend the energy to learn a whole new thing for low stakes deployments.


Uncloud is so far away from k8s, its not k8s like.

A normal person wouldn't think 'hey lets use k8s for the low stakes deployment over here'.


>A normal person wouldn't think 'hey lets use k8s for the low stakes deployment over here'.

I'm afraid I have to disappoint you


It's nice to see some research in this area! As a person that stutters, I find these voice systems somewhere between annoying and unusable (depending on how my stutter is doing on that day).


This.

We're using Google Meet at work and the automatic transcription is completely useless for me, it's not even remotely close. Works quite well for my colleagues.


You can have off-by-default with an allowlist. After the initial period most of your sites that need JS will be on the list.


The Moon doesn't have a magnetic field, though, so the second half of the article discussing difficulties due to radiation would still apply, right?


Not if you bury it in regolith. That’s an idea for a Lunar base too. The design is called “Hobbit holes.” Bury the occupied structures in piles of basically any local mass you can bury them in.

It’s another huge problem for orbit though. Shielding would add a ton of mass and destroy the economics.


Lunar regolith is so abrasive that digging holes or tunnels isn't going to be cost effective.

https://ntrs.nasa.gov/citations/20250000687


We will need to develop very robust, space-worthy electronics eventually. We can't rely on natural magnetic fields forever.


We have them. The RAD750 for example (on the JWST and Curiosity rovers https://www.theregister.com/2012/08/08/mars_probe_cpu/ ) costs about $350k, has the architecture of a PowerPC 750 (the blue and white PowerMac G3), and runs at up to 200 MHz.


We have robust, space-worthy electronics. They're discussed in the article. You just can't get SOTA performance from them, because of fundamental physics-driven compromises.


We have been relying on natural magnetic fields for over a billion years, so we can probably continue doing so for a while.


> Technically speaking, the top of the DNS tree, the DNS root, is a null label referenced by a trailing dot. It's analogous to the '/' at the beginning of POSIX file paths. "gatech.edu" really should be written as "gatech.edu." to make it absolute rather than relative

I have never seen this, but I just tried it and it seems like browsers, even today will happily handle such URLs.

Neat!


If you work much with DNS, you will know about this. It is known as a FQDN, or a "fully qualified domain name", when the name ends with a .

When you don't use a FQDN, your DNS system is going to try to figure out if you mean a FQDN or actually belong to a subdomain.

On *nix, your /etc/resolv.conf file can have a "search" entries for search domains... that means that a lookup for "foo" will check "foo.bar.com" if "search bar.com" is in your /etc/resolv.conf

This does mean your query could end up making multiple queries to determine if you meant foo. OR foo.bar.com

You can configure how the machine makes the guesses with something called ndots... if you add "ndots 3" to your etc/resolv.conf, then your DNS queries will only try treating the domain as a FQDN if it has at least 3 dots... so for example, it would skip querying for foo as a TLD because it has no dots, and assume you mean "foo.bar.com", saving an unneeded DNS query.

This usually doesn't matter to people, but it can have big performance implications for things like Kubernetes, with lots of .svc.local bits being left off of internal queries and relying on search domains; by increasing the ndots, you avoid a ton of wasted queries.


Some browsers (and web servers, proxies, and other things) treat "example.com" and "example.com." differently for various things, like the default limit of per-domain parallel connections. See for instance https://daniel.haxx.se/blog/2022/05/12/a-tale-of-a-trailing-...


They need to, as when the "." is not present, your search domains are used, but they are not used when the trailing "." is present.

For example, if you enter "ajdfajkhdfkajd.com", and your search domains contain one item called "mycompany.tld", then the browser will first query DNS servers for "ajdfajkhdfkajd.com.", and when an NXDOMAIN is returned, they will try "ajdfajkhdfkajd.com.mycompany.tld." next. If you type "ajdfajkhdfkajd.com." in the browser directly, only the first query is attempted.


what's search domain?


The comment explains it.


Presumably they just split the “domain” part out of the URL on // and the first / and feed that into getaddrinfo, with the OS and DNS doing the rest?

But I agree, it’s definitely neat :)


> Even today

It's not like it's archaic. You still use the trailing dot when setting up DNS records to ensure they're unambiguous.


It's that very bottom button you're referring to, right?


Thats the one I specifically mention, sure, but there are many more changes to the page overall if you compare the before and after.


It is not your main point, I know - but for everyone I know who buys lottery tickets, they're more thought of as an entertainment purchase than a financial purchase.


I've heard this argument before about casinos, but never lottery tickets. I'm not sure I personally buy that, but let's go with it.

If they're entertaining, then presumably it's from the thrill of maybe winning. Why would winning be thrilling? Why, because you get money- potentially a life-changing amount of it. If they made a lotto game with a maximum payout of a dollar I'm reasonably certain nobody would play it. Or hell, anyone could write down a series of heads/tails on a paper and then flip a coin to see if they're a winner! Yet, we don't see that, even though it's free and (I would argue) has the same entertainment value.

So yeah, I'm sure entertainment is the facade, but underneath it all, it's financially motivated for the vast majority.


Might tell us more about the people you know than the typical lottery ticket purchaser?

(Or perhaps they're when they tell you it is "for entertainment" they're entertaining fantasies of winning—which is probably what you can say for a lot of people buying lottery tickets.)


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

Search: