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

It's reaching around 50% adoption according to Google stats? Steady growth, though still annoyingly slow. It will need a few more decades at this rate.

> Insatiability

> The nation becomes enslaved to the Chinese leader Murti Bing. His emissaries give everyone a special pill called DAVAMESK B 2 which takes away their abilities to think and to mentally resist.

Interesting. That's quite a bit before 1984 was written.


And Zamyatin’s _We_ was even a few years earlier. Great artists steal.

It's not just that, it's that the topic was extremely actual. Between the Russian Revolution and the general state of European countries at the beginning of the XX century, a lot of intellectuals were working hard on the concepts of "fully rational" societies, fair governance, social efficiency, just social order, and so on.

Somewhat ironically, what seems to have survived in the public consciousness is actually the critique of all those efforts (1984, We, etc). The Western mainstream seems to have abandoned any attempt to create a rational, enduring order from social chaos. Somehow we just accepted that things are fucked up and there is no hope of meaningfully unfuck them.


Those attempts inevitably resulted in fascist dystopias (just look at past and today dictatorships), so critiques of them were and are very on point.

Positive examples that went in other directions, like Huliaipole anarchistic Free Territories didn't survive for long.


Here is a link for people who don’t know about it (it’s not too obvious but “we” is the actual title): https://en.wikipedia.org/wiki/We_(novel)

Published in 1924, it’s a short read, I would recommend, I personally find it more compelling than Orwell’s work


Yes, it's good. Also agreed that AMD would be best GPU experience.

There needs to be a blockade for these rogue ships. That's the only thing they'll understand, short of being sunk.

Just seize the ships and auction them off. Damaging one cable isn't gonna be worth losing a whole ship, generally speaking.

nah just sink them instead imo. they arent worth much.

Given the state some of these ships are starting to be in they might just be worth scrap..

Often the cost to scrap a ship exceedes the value of the raw materials. Depends the ship as well but things like asbestos can drive costs up

Who controls these ships and what is their perspective? I don't understand how we know what they 'understand' or not?

Also, how do you identify the ships? Do you blockade all maritime traffic in the Baltic Sea? All too and from Russia? The first would destroy our own economy, the second is a certain act of war.


Likely Russia. Their idea is to engage in war under pretense that it's not a war.

What I mean is that they will only understand counter measures that you'd take in a war, like blockade or sink them for instance.

I.e. they are already engaging in the acts of war, so it's late to worry about that, the question is what is anyone doing about it.

Ukraine sinks their fleet in the Black Sea, and they understood it very well - they don't leave their ports.


> What I mean is that they will only understand counter measures that you'd take in a war, like blockade or sink them for instance.

Likely that is what they want. Do you think Russian planners are ignorant, and can't foresee that? This sort of game is long played in international relations.

It's chess: You try to cause your opponent to put themselves in a bad position. Provocations are manipulation - it's obvious what Russia is trying to provoke.


I doubt they want that. Blockade will undermine their war efforts which strongly depend on their oil and other exports.

More likely they think countries around Baltic Sea are too scared to offer strong resistance, so they can engage in such activity with impunity. And they won't limit it to Baltic Sea either, they'll do it anywhere they feel they can.

It's a mobster mentality. As I said, the only language they understand is response with force, nothing else.


Russia wants to show global south that the West is evil and aggressive and wants to encroach on and break up Russia. Provoking a European nation into military action first is the way to do that.

Global south cares for Russia as much as Russia is paying (giving discounts) anyone to care for it, not a barrel of oil more.

The most obvious reason here is simply mobster style intimidation. I.e. "You are helping Ukraine? We'll get back at you by damaging cables and what not".

I'd say the proper response to such incidents is to increase military help for Ukraine and blockade / confiscate / sink Russian ships wherever they do this stuff. Ships which engage in that should be treated as hostile military vessels.


> Blockade

That is not an option. They might as well bomb St. Petersburg - it's a seige, an act of war.

> the only language they understand is response with force, nothing else

I see no evidence of that.

Putin is in fact a political operator at a high level, and understands politics exceptionally well. Warfare is merely politics by other means, one tool in the toolchest (for people like him).


That's the only option, because otherwise you are saying that Russia can engage in acts of war against Europe and Europe can't respond. That's not how it should work. And what they do with cables is totally acts of war.

> I see no evidence of that.

Their Black Sea fleet hides in their ports, because they know the moment they'll try to roam, Ukraine will sink them. What other evidence do you need? It works.


Isn't unsafe just for that? Why does it need a separate compiler?

Unsafe isn't so unsafe that it disables the borrow checker!

The two main things the compiler allows in an unsafe block but not elsewhere are calling other code marked "unsafe" and dereferencing raw pointers. The net result is that safe code running in a system that's not exhibiting undefined behaviour is defined to continue to not exhibit undefined behaviour, but the compiler is unable in general to prove that an unsafe block won't trigger undefined behaviour.

You can side-step the borrow checker by using pointers instead of references, but using that power to construct an invalid reference is undefined behaviour.


The borrow checker still applies in unsafe { } blocks. What it means (iirc) is that you can do pointer/memory stuff that would otherwise not be allowed. But you still fully adhere to Rust semantics

Did Japan decide to push proper competition laws?

Time to force Apple to do it everywhere. Very long overdue.


I agree with the “enforce competition laws” sentiment, but in this context, enforced naively, all it’ll do is entrench the dominant browser engine, Blink, even more across the mobile ecosystem.

I’m sure some devs will love this. But equally, some may worry about the monoculture implications.


It hasn’t on Macs. Safari is still popular among non-tech folk

It’s still got popularity within tech-inclined Mac/iOS circles too because it’s easier on the battery than Chrome (+derivatives) and Firefox. Some would like to switch but because neither Google nor Mozilla has much to lose for their browsers being battery hogs, relatively little engineering effort gets dedicated to improving efficiency compared to WebKit (which is similarly efficient under Linux in e.g. GNOME Web, proving it’s not purely first-party advantage).

That’s because Apple adds two extra legs to Safari on OS level and cuts both the legs of other browsers in a manner of speaking by rigging this comparison.

In what way do you think this is meaningfully occurring? I ask because I have not heard of Chrome or Firefox being inhibited on energy efficiency by platform limitations.

This needs a big ol’ “citation needed” slapped across it.

I think the narrative is that once developers have the option to tell all of their users "we only support Chrome, just install Chrome" then any support for Safari will dry up.

Unfortunately I don't think we will see if this is how it plays out until Apple has to allow other browsers globally.


The reason Apple doesn't allow any other browser engines on iOS is due to them collecting up to 30% of purchases made through the apps from the app store. If a developer can do the same things with a capable web browser, then they won't need to create a native iOS app and that cuts into Apple's app revenue. So Apple purposely hobbles Safari so it doesn't have any advanced browser APIs for stuff like bluetooth or other APIs that apps have access to, forcing developers to create an app, where Apple can then cut into purchases made through the app.

It has nothing to do with people no longer using Safari and Apple being sad about that. Other browsers can technically be installed on iOS, but the underlying browser engine is forced to be Safari, which lacks many APIs other web browsers could implement, reducing the need for a native app. It's purely Apple's anti-competitive greed that drives this situation. And the EU, Japan, and the US DOJ have noticed. So far only the EU and Japan have actually taken measures to force Apple to change this.

Here's the entire DOJ lawsuit which includes many other instances of anti-competitive practices by Apple.

https://www.justice.gov/archives/opa/media/1344546/dl?inline


What evidence do you have, other than speculation, that Apple is so motivated? What standard features are missing from Safari’s rendering engine that makes it a less capable browser such that developers are forced to produce apps instead?

WebXR hasn't been supported for 10 years so they control their own AR market.

How does it compare to, say, the experience on Android?

Specifically for me, my company has a product that could use Bluetooth, but Safari will never implement the Web Bluetooth API, where Chrome has for some time on Android. So the workaround is to use Wifi instead (my product supports both bluetooth and Wifi), which drains the phone battery faster.

No, we do not want to write our own iOS app where Apple can then extort us for a percentage of any sales through the app, and we have to pay for the priviledge to develop that app, as well as buy Apple hardware to do so.

So instead we use Wifi, where we can maintain one single codebase - the web application, which works on both Android and iOS, but has to use Wifi. If Apple allowed Chrome to use its own browser engine, we would simply tell users to install Chrome to interact with our device. Then we don't have to pay Apple for anything, nor should we have to.

Apple purposely won't implement some APIs so they can force developers to create an app for their app store where they can collect money from any additional sales through the app. It's all spelled out in the DOJ suit, why won't you just read it??

https://www.justice.gov/archives/opa/media/1344546/dl?inline


We’ve responded to this in a different thread. See elsewhere.

The "monoculture" has never been less of a threat. WPT.FYI is driving towards asymptotically perfect compatibility and behavior. And the real web, the long-tail of websites, is too chaotic to be controlled by any entity regardless of browser market share. Chrome can cook up whatever API they want, no website can be forced to adopt it. And if someone can't use some WebMIDI site on Safari, well, they can't complain, they didn't want that site to exist in the first place.

It's simply not a good excuse to defend the iOS browser ban.


Banning competition can't possibly help increasing competition.

It would be good to see Firefox with its own engine there for example.


I think resolution always refers to physical resolution of the display. But rendering can be using scaling to make things appear to the user in whatever real size regardless of the underlying resolution.

That really depends on the context. Open your browser's Developer Tools and you'll see logical sizes everywhere. Android, which in my opinion has the best scaling model, and where the PPI wildly varies from device to device, nearly always operates on logical sizes. Windows, GNOME, and KDE on the other hand tend to give you measurements in physical pixels. macOS is a mix and match; Preview and QuickTime tell you the physical resolutions, Interface Builder and display preferences will only show logical dimensions.

Linux usage is clearly increasing, so that answers your question.

> I'm not sure what official GOG Galaxy for Linux would add here TBH.

Two major things:

* Backend Galaxy support for Linux builds

* Multiplayer, achievements, cloud saves, etc. i.e. proper integration with optional GOG services for Linux versions.


I think the issue with requests to "release the client" isn't as simple as "you can use an open source alternative".

Their Galaxy backend only handles Windows and macOS builds of games. Linux builds aren't included now. There are hacks around it like using access to individual files over HTTP through zip format for Linux installers as pseudo Galaxy (lgogdownloader supports that) but it's still just a hack.

Another piece is multiplayer integration that games can ship. That depends on their support too (authentication, matching and etc).


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

Search: