FinalBriefing

I think you're thinking too hard about it. It's just a list of R&D projects that might be interesting to some people.

Or maybe they just updated the site in the last hour. It's got a list of team members and events and stuff.

I thought Starlink was supposed to be reasonably priced. Like, wasn't it $99/mo. at one point?

Companies that need to create apps for multiple platforms (macOS, Windows, Linux, web browsers) have a choice:

A) Create separate apps for each platform B) Make one app that can run on all platforms with minimal changes

Electron is a very popular way to build a webapp and make it look like a real "native" app. It is great in concepts: companies can build one app, and they only have to make minor changes between platforms.

In practice, Electron apps hog a lot of memory and can appear slow. Electron is basically a web browser rendering a web page. When you have your regular web browser running, along with a handful of Electron apps, you're really running several comletely separate web browsers all at once. On top of that, Electron is built off of Chrome, and Chrome is a huge memory hog.

So, companies that create Electron apps go that route to save time and resources, hogging up users' resources. For 1Password, it's supposed to be a tiny app the mostly just lives in your OS's menubar or taskbar with a minimal UI until you need to open up the larger window. Instead, there's a whole instance of Chrome soaking up memory in the background while your app is idle.

That idea seems to be ignoring the fact that other brands just haven't made EVs yet. People want Telsas now because, for a long time, they were the only good EVs on the market. As other companies are now rolling out their first EVs, Tesla's market cap will surly go down.

I've also heard the argument that Tesla's network of chargers brings more value, but...there will also be more competitors in that space in the near future (and today).

So, it seems shortsighted to believe that "market cap" is going to remain as high as it is today.

When I look at these proposals, I would still prefer using Sass over regular CSS. It's syntax is just cleaner.

I disagree that it is too tacky for designers. There's definitely a new wave of brutalism sweeping certain circles. I see this type of design in streetware/techware fashion.

Also, it does away with legacy JS imports. It doesn't use or support CommonJS without a plugin.

Nice! Each time I tried out a new bundler (Parcel comes to mind), we hit issues where their configuration hasn't been sufficient for some niche stuff I learned to expect Webpack to handle. I can't think of any specific examples, but I'm sure you've seen something similar.

Vite has been great in the vanilla and Vue projects I've used it for. I didn't think the speed bump would be as noticeable as it was. I'm really happy to hear it is getting more usage in frameworks like Laravel.

It's a JavaScript bundler. If a framework is doing weird stuff with imports, or using legacy module builds, that's on the framework to fix...or not.

Angular is the same way, it has its own compiler and relies on custom build-time code to work. That's also why it isn't picked up by a lot of newer build tools that generally just work with normal JS.

I had no idea so many other frameworks are using Vite as their default. Event server-side frameworks are picking it up!

Has Webpack really been dethroned as the go-to bundler?

I'm guessing that being part of a much larger company allows them to spend more time on UX and "the little big details" that might not directly contribute to profits.

Maybe Github Actions has brought in a lot more revenue, too. They get a "discount" on Azure hosting, I'm sure.

How do you write a CLI tool for viewing a photo album? Would Netflex be better suited as a CLI-only interface?

But aren't there dozens of other companies that sell the same product? Nicotine vape pens? Why is this calling out Juul specifically, and not all nicotine vape pens?

I think it would be a net win for society if the whole concept were killed, or regulated/marketed to help long-time smokers kick their habit. Nobody needs this stuff, even if you enjoy it.

PSI still says you should be using cacheable assets, and the gtag script has no cache-control header. Will users notice? No, but it might play into your score, which does play into your rankings.

I've still gotten a perfect score on PSI with GA enabled, but it is one piece of the puzzle.

No, I don't see any reason to think that. If anything, it will improve your Page Speed Insights score, which will improve your rankings.

Google collects all they need and more from users using Chrome. They don't need GA anymore, and I'm pretty sure they said a while ago they were going to stop looking at the data (again, because they collect far more data from user using Chrome).

Good on you!

Yes, and no. Implementing MVC patterns in React requires developers to architect it that way.

Exactly! I don't know the right solution, either. All the tutorials I've read don't seem to know, either. They're either too simple to where that doesn't become an issue, or they do what you do, and it looks like a mess to me.

In Vue, I'll usually create a service to handle local-yet-shared state (which is just Vanilla JS, no Vue constructs), or create a VueX module (which you could use in React, as well). It's much easier to follow than React's wrapper methods.

In my experience, in both React and Angular, a lot of the things I expect a framework to handle need to be managed by the developer (namely, keeping shared values in sync). Over time, patterns can deviate to where different components/modules use different patterns, and devs spend extra time reading through component files to figure out why their feature isn't updating as expected.

I'm still one of those people. Separation of concerns is a big concern for me.

In my experience with React, it's a lot harder to keep things separated, and developers who I've worked with who have more React experience aren't always up on the concept.

This mindset is why Linux will always have basic usability problems.

> I recommend learning a bit about how your filesystem works and why it can't find linked files from within an archive. This is essential computing knowledge.

Really? Is that _really_ essential computing knowledge?

On macOS, you download a disk image, then drag the icon into the application directory. Many publishers include a shortcut to the application directory and a background image with an arrow and instructions. It's primitive, but it works, and hasn't needed to change in like, 20 years. It requires no knowledge of linked files, or even what a disk image is. Drag and drop. Done.

If you can't install an app like that on most Linux distros (I don't think I've ever seen that), then Thunderbird probably shouldn't suggest that as an option. I've moved away from using Linux as an everyday OS because all these little usability things add up and suck too much of my time.

I've found that SSR is generally quite slow. If you're using it, you'd want a CDN or some other caching layer in front of your server so you don't need to render each page server-side.

Yea...does this mean it will stop working until I pay?

It's been really nice for autofilling console logs and boilerplate code...but $10? It's a novelty that is nice when it works, but that's a steep price point for what it is, and I don't see that changing any time soon.

lol

> Gitcoin grants quadratic funding is not just for funds allocation, it's also a great signaling tool!

Or reddit. I don't see how reddit is any different from Tumblr in this case, and it has several apps. Has Apple loosened up their restrictions since Tumblr went under?

Unions do more than ask for larger wages.

Blog farms are way too popular now, too. People have figured out how Google recognizes "meaningful content", and they generate blog posts and pages with AI and ghost writers to pump out vaguely helpful articles.

Making the Node menu visible at all times might help. Also, some pre-configured demos would be nice to explore what you can create. It's a really neat idea!

I found it to be fast and easy to set up. I reviewed a number of testing frameworks for vanilla JS projects, and it came up on top, even though I hoped it wouldn't (I try to avoid all Facebook products).

I can't remember the specifics, but I think it was a mix of having nice reporting built in, easy to spy on or mock our ESModules, and there are a lot of other developers using it, so it was easy to find solutions.

It mostly "just worked" and didn't require adding other libraries to handle mocks and spies.

That's not true. They might include the tag, but I haven't seen one disable zooming by default.

Fun! I'm going to use this for data in a prototype I'm working on.

This one is cut too short: https://videos.ctfassets.net/bs8ntwkklfua/NiRJbAgDb0L7VWsUfa...

I've found a few more that are also cut a little short.

I don't think that's the case. There are plenty of open source projects that open up Airdrop to devices other than Apple's.