whizzter

Go at it, I have a 1st gen Zephyrus 14inch and had bad heating problems, liquid metal there also initially that just didn't work due to bad application or whatever, repasted it and it's behaved way better.

I was quite nervious, but check Youtube, there's guaranteed some people that has documented the steps, do check multiple ones as some people are more detail oriented or just know what parts can be dangerous/tricky. Good tools can be a lifesaver also (isoprop alcohol for cleaning, lotsa q-tips, good screwdrivers and plastic picks like the fixit toolkits to pry gently).

So basically they'd be new CVE's appearing by the time someone built the previous release at this pace? :P

The tax service here takes money laundering quite seriously so there's been a lot of regulation added for businesses handling cash, most affecting is probably the requirements of "certified tellers" that shot up the price for many smaller businesses (some even closing down or just switching to Swish).

Not entirely sure if those rules were relaxed, but the state and banks with higher cash handling fees did have a fair share in pushing cash out.

Yeah, shuddering at trying to manage memory vs static strings (with OOB risks) in plain C, modern C++ does give so much.

I'm actually also rewriting a header-only server (std c++ and sockets) I wrote a few years back to take advantage of C++26 reflections and similar to give it something similar in capability to AspNetCore+EFCore.

Valuation, by saying that they have something "exceptional" in the works it keeps up the valuation up until the IPOs.

Also, I think programmers/mathematicians (the ones that should be calling out bullshit) are enthralled because many of our jobs was so suitable to automation (this was the secret of the 10x engineers, they didn't shit out too much unnecessary crap.. now that unnecessary crap is spit out at rocket-speed so everyone is working at that speed or even faster).

That said, information-gruntwork that a nominally competent person could do is up for grabs and many previously so called "bullshit" jobs were tied to that.

Sure you can, as long as nobody complains too much about problems during night if those 2 people can work overtime every now and then.

You can probably even promise 99% uptime (sounds good enough to most buyers probably?) even if people sleep 8 hours a day as long as the failures comes no earlier than than 15 minutes into their sleep and only happens at most once a month (1% of 30 days is 7,8 hours).

To be specific, the Amiga scene for a good while chased "coolness" with accelerated "monster"-Amigas.

But the focus shifted in recent years to treating "OCS" (ie "standard" Amiga500 with original chipset and 1mb,etc) more like a fixed platform like the C64 instead and imho has seen a bit of a revival since is mostly in the interesting part of pushing the OCS HW.

Being cycle-accurate is annoying when you want full realtime if the hosting platform doesn't have enough CPU power to emulate all parts at full speed.

I guess the point is that a pre-compiled version could have HW checkpoints from a slow emulated run, so that it can then run at full speed and just advance the HW to the required timestate when a write is to occur (ie, instead of costly cycle-accurate emulationg, most HW operations can be batched inbetween time-sensitive checkpoints).

Then again, why not just record a video at that point? :P

So you're saying I'm hallucinating while working?

No, the debugger (when using Visual Studio proper) breaks at the point of throwing (be it an explicit throw or something underlying like a NPE or out-of-bounds access), _I_ literally use this _all_ the time to fix code while in motion (set next statement on a line a bit back or even the same line to rewind just a tiny bit, change the code, fix errant variables, press F5 to continue and the IDE will rebuild and reposition instruction pointers and update stacks).

What the spec says about execution semantics of exceptions is one thing, what capabilities the debugger provides can be something entirely different.

Perhaps VSCode or some other environments don't have as good debuggers, but trust me when I say that it allows you do do exactly what you need.

Someone saying something in a comment doesn't negate a capability that person doesn't know about.

Companies always prioritize features/capabilities up until shit starts hitting the fan, but even then the culture and requirements makes everything just a job of trying to patch a sinking ship if you're lucky.

Never underestimate the amount of free time a teenager has (both in doing things and teaching themselves), most might not be up to adult levels but many capable ones are far more capable than many adults doing their jobs.

I was offered my first outside job after the second year of highschool, I kinda accidentally interviewed for a at the time respected gamedev firm (since I was looking for a summerjob heh) and when we started talking about when to start and I mentioned my school semesters the interviewer realized that I was younger than he had assumed.

Original source assets isn't really feasible imho, could be custom toolchains and specific compiler versions that things were built with (and breaking on others), sure IF you manage to collect everything to rebuilding (probably needing some kind of VM image to preserve for rebuilding), what's the difference from just making sure the rebuild binaries is capable of running with the prepared assets?

(I'm not looking forward to people automatically AI-upressing of old games, I'd just prefer them to render-upscale and be faithful to the resolutions the games were built for back in the day).

I think they're in the perfect position to take a stab at actually monetizing a "just-works-and-good-enough" local code-assistant that works well enough to save people on burning tokens with the big providers and/or keeping their data offline for regulatory reasons (ie also selling to customers that CANNOT use Claude or OpenAI).

1: Local models are catching up quickly

2: Visual Studio Intellicode (not to be confused with Intellisense) was/is surprisingly good at suggestions (when it first appeared before people went over to CLI's I felt that it was almost magically good for it's time, turned off co-pilot and whatever backend for a reason of compliance for a local workspace and the suggestions are quite good still even if not on the same level as the frontier suggestions).

If it pans out, with their brand people many would probably be happy to fork over for a Jetbrains licence.

No, it's catching/editing/recompiling/continuing at the point of crash, also you can change the current line and variables so many crashes are "resettable" manually.

Visual Studio has done this since the 90s for C++ code (and C# code for a good while also, just most people have debugger exception catching turned off).

How I know? Back in 2000-2001 we were working on a Dreamcast game with a 3dfx/Glide PC renderer, that 3dfx driver on WinNT was unstable and crashed the machine every 3rd-5th start of the game so being able to edit-continue was a damn lifesaver since a lot of common tweaking of custom stuff outside of what connected to the scripting system could be done at runtime.

This is one thing I think so makes people loyal to MSVC despite it having been behind on standards (gonna be interesting to see if they get reflection up to speed for the 2027 release, GCC's there but not yet Clang).

Looking at the behance site it's a pretty good choice, glad some illustrators are still making a living in the AI age.

My best guess would be just the remoteness.

1: Ice-mass that isn't contaminated by atomic testing fallout (if the ice has been there since the 40s it's without radioactive waste (faschinating to read about how WW2 wrecks is a prime resource of steel since it's a huge amount of steel without trace amounts of radionucletiods from testing fallout).

2: No current interference (nuclear power, radiowaves,etc) creating possible test uncertainties.

3: I'm sure there are other reasons

The negative naturally is cost, but since the expriment succeeded it will probably be useful for any attempts to send robots or even humanity into space beyond the solar system.

Asking Gemini it seems their patents covers about 25% of the number of applicable patents, behind them is Samsung, Ericsson and Nokia.

No breakdown on the age of the patents though so it'd be interesting to see how things evolve over the years.

Disabling code is usually safer than enabling, seems they were able to pinpoint this rather quickly.

If they follow the Swish/Vipps method, it's usually connected to your phone so it both enables p2p payments (that Visa/Mastercard doesn't offer), but also QR-code based payments (scan-and-sign) that are complexity-wise about the same as Apple-pay,etc (usually with a bit higher security requirements).

Since Wero (that is included in the new initiative) already has a mass from Germany and France, including Spanish and Italian operators more or less locks down something without major competition inside the EU market creating something universally useful that now has a large enough mass to become the defacto standard.

Notably absent is Swish (that is probably the oldest banking-backed mobile payment app in Europe operating since 2012), they were kind-of-interested in cross-transactions when the Vipps/Mobilepay merger also connected with some Finnish party but iirc nothing happend.

No idea if it was due to hubris and protecting their own market or feeling that technology matching was problematic (Swish has a bunch of features like corporate reciving/payouts, payment-requests,birthday cards, receiver identification,etc that might or might not mesh well with foreign providers).

Mastercard pretty much depended on Eurocard/Europay for it's European reach (and vice versa) before the 2 merged, European institutions didn't have a problem selling out important infrastructure because Europeans overall trusted American stability and cooperation.

If they're all downstream users and rebuilding their entire infrastructure on Clang might not be the most enticing thing if they're deeply embedded into EDG in their products and EDG can be kept alive with small costs per company.

I think that's the point of the whole point of a nonprofit stewardship, that a few developers each from the main customers can come together and cooperate well enough on the upstream that they don't have to take the entire cost of changing downstream to Clang or maintaining a frontend.

Maybe they're hoping the remaining customers will cooperate on keeping it up to speed? I know that f.ex. IAR are building their own backends,etc and might be an EDG customer, the MSVC IDE team aswell, now if they'll manage to get it working is another question but with the code in the open there's a chance at least.

Why not defect to clang? I'm sure some PHB's will suggest that (and that will be part of the survival, convincing those that supporting another party is a good thing).

Standardization does have it's issues, but the JS ecosystem always seems to be healthier when one implementation isn't too dominant. The question is if the C++ ecosystem is large enough to support multiple frontends.

And that's a thing though, SFINAE hinted at it but more recent versions of C++ constexpr and consteval together with relaxed constexpr and "if constexpr" and "if consteval" together with compile-time dynamic typing forced the compiler to more or less include an interpreter in the frontend.

Adding some features of C++11 isn't close to building a C++ compiler capable of 11, 14, let alone 17, 20, 23 or 26.

If you can rip out a compliant parser, it might even be better to start over on a new compiler frontend if your current compiler frontend is targeting at pre-11 level.

Building a company is so fraught with pitfalls, probably realized at some point that their income was good enough that they could safely work towards retiring at some point in the future without problems and drama.

... or why it's best to just use the OS libraries to render to textures if you only need an OSD :P

Question though, you implemented the slug system? The article mentions root eligibility but doesn't expand on it, what's the point of it because slug doesn't seem too "magical" for only doing winding counts?

1: I think that's still a decision of the OS developers, you can have a purity-of-install to have functioning software (avoiding incompatible libraries), in the end though for all binaries it's just instructions with little knowledge moving around an instruction pointer, so is there anything fundamental that precludes an overlayed patch-stream where you have installed versions (nix world) but a runtime linker that silently replaces core libraries (that would cause extensive reloads, say OpenSSL) during link-time to have a functioning userland until the next release occurs?

2: I hear you, I still think it's a minor inconvenience in the grand scheme of things, worst case administrators should manage for full user backups in case of breakage (people bad backups habits are more likely to cause havoc for other reasons like hardware failure than the occasional downgrade of system data).

3: only thing that immediately comes to mind is Blender, but there it's Python scripts and intentionally not supporting C++ plugins (last I checked you're supposed to rebuild the entire thing if you want C++ additions).

4: OSS unixy systems has always had tilt to the former in the conflict between the security/sysadmin view (no local binary searching due to security, binaries upgrade everywhere) vs users (who wants to run programs and don't care too much about what glibc version it was compiled with, even taking that big binary with all libraries bundled).

I see Nix as more like Windows SxS instead of just shipping everything like with flatpak,docker,etc. But it always boils down to the same dependency on absolute filepaths for everything that's hard to escape (because you can "just recompile").

flatpak exists though, doesn't it work well enough?

1: Sounds like something that could be improved rather than being something inherent, could be part culture though since slightly incompatible C/C++ libraries isn't an uncommon thing so unless there's proper testing channels the user-diskspace/time is a tradeoff (not perfect, but reasonable)

2: Doesn't really sound like a problem for most desktop stuff unless there's some components you use that depend on non-upgradable data. Users have their browser, word files, excel files, pdf files and so on.

3: Sounds annoying, but also like a fixable feature. How much common user software have native plugins ?

4: Binaries for Linux is a bit of a mess in general, I think someone in jest wrote that now that Wine has improved, win32 binaries is the preferable binary distribution format for Linux.

Seems like recycling is picking up for lithium batteries and the metal components are still valuable enough.

I think a bigger question is if sodium batteries starts to take over (seems better for homes, heavier but seemingly safer but also for cheaper cars) and lithium/rare-earth metals prices goes down.

Perhaps why they're forking it?