mzronek

For downloadable software there is the risk of a supply chain attack. The website is altered to provide a download with a malware-infected version of the software.

See the recent hack on CPU-Z: https://gist.github.com/N3mes1s/b5b0b96782b9f832819d2db7c668...

Americans will measure with anything but the metric system.

Luckily DX is much better now with Turbopack as a bundler. First they improved the dev server, now with Turbo builds the production builds are faster as well. Still not fully stable in my opinion, but they will get there.

It's also wise to use monorepo orchestration with build caching like Turborepo.

They did well on the turbo stuff, no doubt about it.

The main bottleneck with big projects in my experience is Typescript. Looking forward to the Go rewrite. :)

I am still waiting for the Smell Blaster.

That's part of the vibe in vibe coding.

He also casually dropped that he talked to people at firms with "high amount of coding", who told him that by the end of this or next year "most code will not be written by humans".

Yeah, okay. I work each day with Copilot etc and the practical value is there, but there are so many steps missing for this statement to be true, that I highly doubt it.

My case is, wouldn't we already see the tools that are at least getting close to this goal? I can't believe that (or AGI in fact) to be a big bang release. It looks more like baby steps for now.

How do you get the server-side data to client-side Javascript? For example an array of strings or an object.

With Full-Stack React you will use JSX to directly render HTML. Logic is done with Javascript, so you don't need to learn an additional language. There is also no mapping to Javascript and you can use the standard toolchain (for debugging).

Using server-side templating is another layer of complexity on top of your stack, that just glues together your output. These template languages are not easy to learn. Custom code for loops, escaping, template inheritance etc. Sometimes these are also hard to debug. The documentation of Jinja is huge.

Things get worse when you bring Javascript into the mix. You need to create Javascript code with your template engine without any Javascript toolchain.

Hard no to the string concat approach for me.

You can opt out by using a single (optional) catchall route and handle the path all by yourself. This is sometimes necessary to handle CMS pages for example.

Docs: https://nextjs.org/docs/app/building-your-application/routin...

They seem to recently position themselves as a Wordpress alternative. There is a blog post about migration from Wordpress to Payload including code: https://payloadcms.com/blog/how-to-migrate-from-wordpress-to...

No, it's a Headless CMS, so no frontend themes and templates. They have an official demo page including a frontend, that you can base your work on: https://github.com/payloadcms/public-demo

If you are looking for a Wordpress-clickety click solution with templates, Payload is not a candidate.

A common misconception. React is a library.

These are examples for React frameworks: https://react.dev/learn/start-a-new-react-project#production...

Next.js is a React framework.

If Payload is a framework or not is debatable. I think it's more like a data layer around a database for a any js app and an Admin Panel (that uses Next.js now). It might be called a framework for your own Headless CMS, because it is code first. So you basically code the panel and the data structure yourself.

I reviewed hardware back in the day and was tired of all the repetitive tasks necessary to measure the performance of CPUs, GPUs and storage devices. So I wrote a benchmark automation tool, that did the work for me.

CINEBENCH and the likes where easy, but I also automated games without using their integrated benchmark. I needed a scripting language to load settings, go through the game's menu and load a save game. To avoid any kind of load from the automation, it offloaded the input data to an Arduino-based USB device, that simulated the benchmark run with previously recorded input. It worked pretty well, but small latency issues could of course result in small variations of the run. And bouncing into NPCs was generally a bad idea.

Here is a video of the system in action that completely automated a custom CS:GO run with additional streaming load as it would occur when streaming PC gaming: https://youtube.com/watch?v=ZpSPyd9f4cg

I get asked once in a while if the software can be downloaded or bought, but I am not going to do it. Writing software for yourself has the neat advantage that you never need to deploy it, upload it, write a change log, answer questions or fix bugs at any given time. It is just about solving the task at hand and nothing else.

Things is a great example for PWAs, because it does not exist on Android, Linux or Windows. It could be though, if it would be a PWA.

It is not and it seems like the developer focused its resources on native software for Apple products.

The author argues multiple times that Next uses the React canary release channel and that's unstable. I think the name for this release channel might be misleading:

"We’re introducing an officially supported Canary release channel for React. Since it’s officially supported, if any regressions land, we’ll treat them with a similar urgency to bugs in stable releases."

And:

"Unlike the Experimental channel, React Canaries only include features that we reasonably believe to be ready for adoption. We encourage frameworks to consider bundling pinned Canary React releases."

While I think that Next.js 13's release was bumpy and about a year too early (let's blame it on the VCs), the App Router is in nice shape today and ready for production. It has a steep learning curve though and your brain needs to painfully unlearn some well-established patterns.

Source: https://react.dev/blog/2023/05/03/react-canaries