spystath

You are right that it's due to housing but in my opinion most of unaffordability comes from immense pressure due to tourism. Housing situation is better outside the touristy areas (and Athens). If anything Greece has seen massive housebuilding up until the economic crash in the early 10s. I remember block of flats appearing left and right in most major cities in a span of months. They still do but in a lot of cases they are almost exclusively short-term lets (again especially in tourist hubs). Why let a flat for €500 monthly when you can charge €150 per night? It's maddening.

Obviously installing anything from AUR must be done cautiously and there have always been sketchy (as in improperly built/packaged) packages in the past but seeing actively malicious injections is concerning. I think there are two main problems with AUR: 1. it is a remnant of a slightly more egalitarian era in the open source history when you could generally trust 3rd party code and 2. orphaned packages can be adopted by anyone with their full history and vetting intact.

I think we are well past (1) but (2) could be mitigated by tighter controls on AUR accounts and potentially additional safeguards from AUR helpers. Maybe show a big scary warning if the package has changed owners recently. I know there will still be people that will "y" their way forward but it's better than nothing.

Or just avoid AUR helpers altogether and inspect/build the packages you need yourself from their PKGBUILDs directly.

There are not enough words to describe how much I hate Akamai EdgeSuite. So many random validation loops and 403s across different physical computers, different operating systems, different connections and even countries. A couple of services I need use it and it's 30% I'll make it past their stupid "protection".

Despite the HN title (and while the focusing optics are similar), the structure in the article was directly milled with an ion beam (FIB), not electrons.

There is an implicit shame in disgrace but faceless entities have no shame. They'll just put out another press release written in corporate newspeak by an LLM and move on withe the plans anyway. This is standard Google behaviour. They do it with Chrome, they do it with Android, they'll keep doing it with all their captive markets. I fear that in practice even having an "advanced flow" will make little difference as some applications will refuse to work if you have it enabled anyway (in the same vein if debugging is enabled, for example).

Nothing about Android is open except the absolutely minimum amount of linux kernel that's required to boot the thing. Then it's blobs and restrictions all the way to the screen.

Alternatively: https://xon.sh/

Chrome is the dominant browser. Sad as this may be removing it from Blink means de facto removing it from the spec.

That being said, I'm not against removing features but neither this or the original post provide any substantial rationale on why it should be removed. Uses for XSLT do exist and the alternative is "just polyfill it" which is awkward especially for legacy content.

In a lot of cases on a residential line you can't even pay for a public and/or static v4. The option simply doesn't exist. Many ISPs just force you to buy a "business" package for 3x the cost with a bunch of other features you may not need.

Issue (1) has been a long-standing issue and a prolonged back and forth [0,1] between NVIDIA and Xorg/Wayland devs about implicit and explicit synchronisation protocols. It looks like the explicit sync protocol is in the process of getting merged upstream and the 555 series driver [1] will take advantage of this so hopefully things are looking better. Problem with wayland is that all of the driver, xwayland and every compositor must support the new protocol but it looks like mutter, kwin and wlr will eventually support it. That being said there are constantly new paper-cuts appearing with the NVIDIA driver and Wayland support so who knows what will break with the new driver. Definitely not a pleasant experience. I'm not saying that AMD is smooth sailing but at least you don't have to fight the driver at every new release.

I'm afraid (2) will probably never work properly :-(

[0] https://gitlab.freedesktop.org/xorg/xserver/-/issues/1317

[1] https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests...

[2] https://github.com/NVIDIA/egl-wayland/pull/104#issuecomment-...

You don't have to use a browser. I had very good results with Weasyprint [0]. And there's also PrinceXML [1] if you're willing to pay.

[0] https://weasyprint.org/ [1]: https://www.princexml.com/

I think that's a relatively simplistic way of viewing this. Although I don't disagree with the core argument, Google will always implement and ship "standards" that fit their business model or their vision of the web. A Chrome API becomes a defacto standard regardless of the state of consensus between engine vendors. Chrome can bulldoze through the standards process because of the massive amount of Chrome installations (and derivatives).

There are standards that have never been fully accepted by Mozilla [0] or WebKit (famously webusb for instance, because of security implications) but they are still in Chrome and now Firefox or Safari are effectively a "worse" browser because they don't support "standard" X that never reached consensus but Chrome implemented anyway. It always starts as an "experimental" feature under a config flag while the supposed discussion is taking place "just to see how it works, promise" before Google decides to remove the experimental flag and ship it. WEI started to play out exactly in the same way but given the massive outrage they decided it was too damaging to keep pursuing it (they still sneakily implemented it in Android WebViews).

So although I don't disagree that, yes Google has certainly improved on some things when it comes to standard processes they have abused their powerful position and continue to do so to push forward whatever they think it benefits them.

[0] https://mozilla.github.io/standards-positions/

Oh yes, I understand that. I only wish that ECC support in general starts getting more traction in consumer electronics. Nowadays (unless you go to super noisy super expensive server hardware) maybe with an AMD processor maybe a motherboard manufacturer will have a 20-links-deep document that says that these ECC modules may be supported, proceed at your own risk, might set your flat on fire, kill kittens etc. When you had a couple of gigs of ram it was probably irrelevant but if you have multiple TB of RAM caching file access ECC should become normalised.

More RAM is always nice but I'm secretly hoping we'll start to see more ECC support in the future. With these humongous modules and even with a teeny tiny bitflip probability corruption chance becomes non insignificant.

The hold-back feature is so extremely out of touch with reality

"There seems to be something wrong with your request, try reloading this page"

Good luck getting this ad infinitum you are on an environment that Google doesn't approve.

I was there too, in the 1.0 days, and still am. But these days are gone, Firefox is not coming back. Back then Firefox was immensely better than IE. As long as the other alternatives are just as good, there is no reason for the mythical "average user" to change over. Why bother if you can do everything in Chrome? We may understand the differences, ideological or technical, but good luck explaining that out there. There's a massive disconnect between user and technology and as a result people will live in the perfectly curated technological bubble that's been served to them.

how do we protest this?

You do not and you cannot. It was written in stone once Chrome dominated the browser market. What Chrome (Google) wants, Chrome (Google) gets. Despite all the good engineering Google wants to sell ads, that's all there is to it. And the result is this proposal.

The saving grace here might be that Firefox won't implement the proposal.

It's irrelevant and we are an irrelevant minority. Unless people switch to FF in droves the web is Chrome. And they won't because at the end of the day people just want to get home from their shitty jobs and stream a show. As long as that works everything else is a non-issue.

They closed the gates when their specific niche has been captured so that they can extract maximum value. As a result interoperability between services is dead. Fediverse is a valiant effort but the barrier to entry is relatively high, even for techies. It's time to accept that people just like the "comfort" of walled gardens.

Regardless of the DE preference I believe the Gtk/GObject/GLib ecosystem is quite well designed and it's relatively easy to reason around and get into developing with even without using C since there's a ton of available bindings. KDE development is tied to the Qt framework which is essentially C++ only (with Python bindings for the Qt libs). The language is based on pragmatic requirements and I can't see any correlation to the quality of the software.

It may happen eventually but they have no incentive to make it so. They've captured a significant part of the corporate market by bundling with O365 for Enterprise. Teams has fulfilled it's purpose just as Office did. At least Office is decent software.

I don't think that's true since about a year ago.

https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests...

I know it's been repeated a million times by now, but NAT is not a replacement for a firewall. Most residential routers are deny in by default so you get zero incoming connections from the internet unless you open the relevant ports, exactly as with NAT.

Unfortunately at 4k nothing over 22" is 200+ dpi. It's definitely better than the run of the mill 90-100 dpi monitors but not enough to fully eliminate the need for AA. You need to push around a great amount of pixels to have crisp text with no AA. Presently 5k desktop monitors go for $2.5k+, 8k for $4.5k, which honestly is not terrible but still quite expensive. Even those are at 32"+ which defeats the purpose (stil below 200 dpi). It seems like the desktop display industry is not interested in pursuing this, going instead for faster refresh rates, as such it's unlikely that we will see 250+ dpi displays on anything other than sub-15" laptops and phones.

Powers my router, running on an APU2. The run-from-ram-with-overlays configuration makes upgrades relatively painless.

Teams, Slack and Discord don't want to talk to each other. They want their own silo with their own users. XMPP, Matrix, or anything, for that matter, can't fix that.

Well, manual interventions are rare [0] and almost all of them nowadays are due to the odd package restructuring. Usually the package manager will notify you about a conflict between two packages and won't proceed (so nothing will break). At this point you can check the website if there is a need to force install a package or two.

Although definitely more technical than most distributions the perceived difficulty of Arch is mostly a meme at this point. The last large possibly-system-breaking change was almost 10 years ago [1]. And even then, the solution was quite trivial. Now if you are forcing updates that conflict without reading the news then you're in for a bad time, but that's true for all distributions. In general pacman is very conservative and won't leave your system partially updated. Now there is a chance upstream updates break things, but that's the nature of the rolling release model.

Manual compilations are not necessary if you stick to the official repositories. If you need a package in the AUR then a ports-like setup is required. I have packaged stuff for both RPM and DEB-based distributions, nothing really beats the simplicity and flexiblity of the Archlinux packaging tools.

[0] https://archlinux.org/news/

[1] https://archlinux.org/news/the-lib-directory-becomes-a-symli...

One is their DirectX extension that only works on WSL2. It allows you to access the DX API through a shim driver. You can now have a Linux application that needs access to /dev/xdg which is only available in WSL2.

https://devblogs.microsoft.com/directx/directx-heart-linux/

For every couple "just works" cases there is a corresponding "doesn't work at all". Given the diversity of the PC as a hardware platform there are going to be edge cases. There is no avoiding that. I'm fairly certain there are cases where hardware "just works" on Linux but doesn't do so on Windows either because there is no driver any more, or because the driver is borked, or any other reason. And here's my anecdote: the wifi on a windows laptop I had once kept dying or dropping packets randomly. Turned out the shitty Killer wifi driver was doing some kind of "optimisation" <insert hand-waving here> to improve throughput. It took a lot of google-fu to find out what the problem was. And this is where I believe you are wrong wrt the command line. The command line is a powerful diagnostic tool and having text files as configuration is much more accessible than delving into a 13-level deep registry chain.

Now, I'm not claiming that everything is smooth sailing on Linux, because it isn't, but the "I've spend hours trying to debug something" argument can be said for both sides and if it comes to that the mythical "average user" won't be able to sort it out by themselves in either case, command line or not.

In reality the Linux and web versions are not similar to the actual Windows client. For instance the Linux version is stuck to 2×2 video streams at best, doesn't support background blurring, audio/video quality is inferior, doesn't support sharing a single window, no breakout rooms etc [0]. None of these are of any considerable importance to me but Linux or the web has never been priority for Teams nor will ever be. In fact I will not be surprised if/when Linux is dropped completely when transitioning to Webview2. Judging by the "PR-speak" [1] this is what probably will happen anyway.

[0] https://microsoftteams.uservoice.com/forums/555103-public/su...

[1] https://github.com/MicrosoftEdge/WebView2Feedback/issues/645...

On some linux distributions [0] microcode is loaded early during kernel boot. So it's a matter of pinning the package to a previous version. No idea what happens with BIOS/UEFI updates though, although you can roll these back too. Obviously the "proper" way here is to have open source microcode but I can't see that happening anytime soon.

[0] https://wiki.archlinux.org/title/Microcode#Early_loading

This might be me being pessimistic but there are no web standards any more. It's Chrome standards. You can fall in line or drift into obsolescence. We never really got rid of the IE dominance on the web, we merely exchanged one boss for another. I get it it's not _quite_ the same since we don't have the ActiveX nonsense any more but it certainly feels like we're living in Google's vision of the web. Monocultures are harmful but that's we get to live with.