chaosharmonic

> Bans should not be for all products for life. Please reconsider this approach, adding a navigation bar to a mobile app should not result in someone being unable to monetise free educational content they produce on Youtube.Likewise if I had received a developer account ban, my personal account would have been banned by association removing all access to other apps which use Google SSO. That is also a grossly unfair practice which could be improved upon.

^ This right here is also why friends don't let friends use Google's password manager.

> go play DDR

Can confirm, this is one of the only things ever to get me willingly doing cardio on a regular basis.

It also spawned several technical projects: I built a control interface for a Cobalt Flux from parts, finally learned to solder in order to fix a panel on it, and built a small workout tracker as a MERN stack demo and progress log (when I still had a place I could play DDR in...)

Which brings me to the piece I'd add to this:

Build the things you want to use.

Also Deno (along with Bun) did pull Node in its general direction -- the latter has finally started to ship things like test runners, a watch mode, and Fetch

If you have a problem with that, why limit this to TikTok?

Not that it isn't at least a little reasonable to be wary of adversaries having access to a data collection platform, but the problem also gets meaningfully less substantial in general if you put meaningful limits on these companies' capacity to grow and eat each other in the name of building empires of surveillance capitalism.

Meta in particular is pushing hard on that angle while hand-waving away the fact that Facebook has a history of treating society as a large-scale experiment. It's manipulated users' mental health on purpose, meddled in elections by selling users' data directly to campaigners, and furthered incitements of everything from genocides abroad to the attack on the Capitol. They're feeding into attacks that single out TikTok specifically, as part of a broader pattern that Facebook and Zuckerberg personally have exhibited of trying to buy or clone nearly anything that represents competition. They bought Instagram. They bought WhatsApp. They tried to buy Snapchat. They've lifted the primary functionality of several large competitors, ranging from disappearing messages to basically all of Reels.

Instead of just taking the blunt-instrument approach of banning social media platforms from within the borders of specific foreign countries, we arguably should be having an entirely different conversation about banning the business practices that make TikTok a problem.

> One cool small detail on the 16" is they've dropped the built-in 3.5mm jack and added two more expansion card ports, with one of the options being a card with a 3.5mm jack. Really smart move there; satisfies both camps of people who want and don't want that jack.

Normally this would annoy me a bit, but my 11th-gen has always had a bit of annoying line noise coming over the headphone jack anyway, so being able to break the whole of that out into USB is actually a compromise I'm more than willing to make. (Also I lol'd IRL at the riff on "courage.") But then again, my hot take on phones for a while has been that I'd rather have two USB ports than one headphone jack, so this is pretty firmly in line with that.

> I think the thing that is most encouraging is that it does seem like they're trying to settle into a yearly cadence for new mainboard releases, tracking the latest chipsets from Intel (and hopefully now from AMD too). I was a little worried that they wouldn't be able to keep up, since they're still a small-ish company. Certainly not going to buy the 13th-gen or new Ryzen boards this year, but it's good to know that, assuming the company continues to be successful, I should be able to upgrade in a couple years.

My guess is that would actually be less of a problem in this context, given that the the form factor is stable from year to year and they can just ship upgrades for individual components instead of making whole new devices on an annual basis.

I personally held off on getting one until my previous device (a Spectre x360) got smashed up in a car crash, but don't in any way regret this purchase even if I do still sort of miss touchscreens (and probably also would have waited for an AMD option otherwise).

But yeah, when I was suddenly in the market for a new laptop anyway, the extensive freedom to upgrade and configure this made it an extremely easy sell compared to anything else that would have been on my radar.

That's less of a distinction with 32- vs 64-bit for me (though I know that does also pose issues for, say, users of any Raspberry Pi other than the 4B/CM4) and more that there just aren't any first-party ARM builds for Linux.

(That said I can't really speak to macOS here, as I really only use Macs when workplaces require me to, which also doesn't necessarily translate to having sudo access.)

I'm a huge fan of it personally. To me, relative to Node the way this handles feels, broadly, closer to a browser -- by leaning on Web standards there's a variety of knowledge transfer between client-side work and server-side for things like packaging, API calls, and various other functionality; and it builds in enough basic tooling that I don't have to find or install or develop opinions on external libraries for handling anything from watching files to using environment variables to running tests (if I necessarily cared to do that with personal projects).

The limitations that stick out most to me personally are that there's still no ARM support, and that, while the Node compat is getting a lot better, it's still hard to get a clear sense of where it is for individual packages -- what runs natively/is isomorphic, vs what'll run under a compat layer, vs what just won't run at all.

Yeahhhhhh, not that there aren't totally valid reasons to opt for pseudonyms, but I also see a lot of overlap here with the Lorenzo Von Matterhorn.

> One day people and institutions will get the message and stop using Google for important things.

I've taken to telling people for years now, for this exact reason, that friends don't let friends use Google's password manager.

The century the test is being administered in?

An accredited CS degree program is actually one of FreeCodeCamp's long-term goals.[0]

[0] https://www.freecodecamp.org/news/free-accredited-bachelors-...

I mean, the restaurant industry is getting hit disproportionately by employees leaving in droves...

I'm sorry, but Uncle Enzo and I go way back, and I couldn't do that to him -- not after I already promised him I'd go to the job fair coming up.

The converse to this is that a resume gap can often stem from things like family status, or health conditions.

Stuff like this (at least in the US) is supposed to be legally protected, but in practice it's a little useless to bar employers from, say, asking about your medical history if they can push yourself to explain a gap in your resume that was exacerbated by a mental health condition, or caused because some illness or accident or left you physically unable to work. (See also: candidates who have kids)

It's a dumb loophole that enables hiring discrimination -- because you can still fish for information that's illegal to ask about specifically, just by falling back to a catch-all question that's bound to turn up much of the same information a meaningful chunk of the time.

I've toyed around for similar reasons with trying to get Melee Light running on a local in hopes of at least getting its codebase up to modern versions of JavaScript and the dependencies it was using, but it's larger in scale than anything I've ever previously tackled solo and I'm not even sure what thread I'd even pull on to untangle the build config, let alone everything else.

An interesting concept actually occurred to me on this same idea, albeit still sort of blocked by the first thing -- what if this or an engine like it were moddable on purpose?

An open set of tools for generating character data or making engine customizations could actually open up a lot of possibilities around more easily implementing roster additions or even just enabling total conversions that are less likely to get DMCA'd.

I semi-regularly wish I lived on the timelines in which Star Wars Battlefront III and MegaMan Legends 3 hadn't gotten canceled.

> The mainstream media did a great job of outraging liberals because whenever trump said anything even remotely controversial, it was covered nonstop until he said the next thing.

To be fair, I bet you could measure the average interval of those events in hours.

It's a pretty ergonomic way of scripting smaller tasks, at least. The first time picked it up for the sake of a meaningful experiment I stopped short of actually deploying a full project on it -- the key limitation being that I couldn't find anything comparable to Mongoose -- but did end up building a companion tool that turned out to be pretty useful, and for stuff like API calls and bulk file manipulation I would reach for it every time.

Specifically, it was a minimal simfile parsing/conversion/seeding tool, as part of a DDR workout tracker I was working on a while ago. (Everything from COVID to a mouse problem in my workspace kind of undercut me doing the cardio I had built it to track, so it sort of stagnated :-/ But the tooling itself was pleasant enough here.) Basically it had three core pieces of functionality:

- Parsing .sm files and converting them to .ssc (the former doesn't label its fields, so doing this first simplified everything else)

- Extracting metadata from simfiles in .ssc format and exporting it to JSON

- Uploading extracted metadata to the accompanying API

This is something of a moot point since it's been added to Node now, but at the time having access to server-side `fetch()` also saved me some frontend work, because then all of my client-side requests became isomorphic and I could just mock out what I was eventually going to need for my UI without actually having to make any other decisions about how the UI was going to be structured.

Proton also depends on DXVK, an additional translation layer that specifically bridges the Windows graphics APIs to Vulkan (as opposed to WINE handling its system calls in a general sense).

Meanwhile, newer versions of macOS (and the M1 that runs the ARM builds in particular) don't use Vulkan at all, opting for Metal instead.

Super M1 Turbo HD Remix

I'm not sure if you're saying that stumbling across this site will ruin my life, or enhance it....

Does this not persist when you navigate around? I've only ever seen the page contents here -- including text input values -- change if I explicitly reload. I haven't looked in any detail, but based on the behavior it seems to generally be getting cached in the browser?

(Though it does seem to be an HN thing specifically, and yes, I would absolutely dread this if I were typing a draft anywhere else)

The difference is that, relative to the days of Windows 8, they've significantly diversified the ways you can target Windows, directly and otherwise:

- IE is finally dead, and shipping a downstream Chrome build in the form of Edge gives Win10/11 not only a revamped WebView but platform-level support for PWAs (I cannot stress enough how much of an impact there is here just from how much the Web has evolved as a platform, and as a Linux user this cuts both ways tbh)

- To this same point there's also a first-party React Native build, allowing devs that are already shipping mobile apps to extend those to target desktops

- .NET has since been open-sourced, gone cross-platform, and picked up native ARM support

- Windows Subsystem for Linux, and now Windows Subsystem for Android, let you reach outside the Windows ecosystem entirely (the latter of which, interestingly, should also compound over time with the various efforts that Google is finally making again to make large form factors viable on Android)

- Project Reunion exists now, for the stated purpose of providing a common set of APIs that Windows developers can access

That last one alone, btw, makes the landscape inherently different from WinRT, which removed Win32 support entirely and only allowed you to run UWP apps.

Cool. Are there any plans in the future to ship non-Intel options?

Curious about this too, as well as if the pack is a single unit or a set of standard components that you can upgrade individually.

Not necessarily. Strictly speaking, the E2E part is being added via Google's network and isn't part of the spec. It's using the Signal protocol, which is just as open for Apple to use as it is for anyone else, but it doesn't inherently come with every RCS implementation.

It actually extends further -- QTWebEngine is now a stripped-down version of Chromium.

So to be clear I generally agree w Amadeo's point, as I'd much rather see every chat network built on top of phone numbers die out like the widespread use of ICQ. Personally I'm much more interested in seeing something like Matrix take hold, because to me a Web-based model, with some sort of user@site identifier and, incidentally, the ability to deploy one yourself, are non-negotiables for anything I adopt as a primary communication spec in the future.

But this isn't about the use of Web-based services, this is about a text client. That's not going to just disappear anytime in the near future, it isn't reasonable to compare them to better chat networks when we're specifically talking about fallbacks, and whether they have incentive to implement a standard for it doesn't mean they should just have free reign to promote ecosystem lock-in for the basic functionality of a phone.

And do I also agree that the implementation of RCS has been less than stellar, but that's in part because of fragmented adoption among vendors, which is a problem that Apple is a part of.

(And speaking of ways that markets are worse because they don't have "incentives" to adopt standards, I forgot to mention their continued use of Lightning.)

> Also blue texts

Not that Google has an attention span here (I'm still annoyed at them for what they did to XMPP), but RCS exists, and Apple is perfectly capable of at least supporting a fallback spec written this century. Their choice to instead just actively degrade the messaging experience, for everyone involved, when anyone involved isn't their customer, makes the entire market worse.

See also: Safari