richeyryan

It seems like the move is to force ByteDance to set up a company incorporated wholly in the United States, which would then be subject to the oversight of the US government. Then, Byte Dance would lease the IP surrounding TikTok to this separate company. All the US customer data would be siloed on US servers and perused by US agencies and Byte Dance would still get their revenue from the US market. I don't know if the close association with ByteDance and China would still make that sort of arrangement a target of the US government.

I suspect they want better condition handling. Because JavaScript lacks a useful conditional expression beyond ternary expressions, condition handling in JSX generally uses boolean operators or ternary expressions. Suppose the conditional logic is in any way complex. In that case, your choice is to use nested ternary expressions, which can be hard to read or to somehow break the condition out of the JSX using a helper function or separate component so you can use if statements in a regular function context. SolidJS added conditional helpers to its JSX flavour to address this issue[1]. The React team seems ideologically opposed to the idea as it presumably moves JSX away from using only JavaScript for handling logic.

[1]https://www.solidjs.com/docs/latest/api#show

Most computer users don't use command-line apps day in and day out. Most computer users nowadays use chat apps (Discord, Slack, Whatsapp) and have probably encountered bots on those platforms before. There is an inherent familiarity that makes it feel more accessible.

Substitute software for standard accountancy practices or a filing system that led to lost files, giving the incorrect impression that postmasters were stealing, and the result would have been the same. The core issue is an organisiation that values avoiding blame at all costs over transparency and accountability.

It would be nice if the author would add mozjpeg[1] to the comparison. At certain image resolutions, it can produce smaller file sizes than WebP, and because it is still a jpeg, it has a much better compatibility story, which the author alluded to.

[1]https://github.com/mozilla/mozjpeg

I think the use of template strings simplifies it, even inline:

const { status } = await send(`${capitalize(greeting)}!`)

console.log(status)

It does reduce the number of discrete operations to make the pipe example look more impressive, though.

Perhaps this falls into the repetitive boilerplate category you referred to, but if you want framework-agnostic domain objects that still work well with Svelte, create your own using the observer pattern.

Create an object with a subscribe method and whatever other methods make sense for updating its state. Svelte will treat it like one of its stores, and it will work with the $ syntax. It can be used with React via its `useSyncExternalStore` hook. It can be used with SolidJS via its `from` utility.

If you don't want to handle the set-up boilerplate, you could use another library like Effector or RxJS, but of course, that means another dependency. There is a gradual move to make something like this a part of the platform[1], but who knows when or if it will land.

[1] https://github.com/domfarolino/observable

In my experience, the quality and depth of my code reviews were a main contributing element in my last promotion conversation for a senior+ role. It wasn't even a metric I had to scrounge up but something my manager proactively raised to justify approving the promotion along with other criteria. Other team members reported to him that my feedback helped their growth.

However, there is an aspect of being in the right team and company at the right time. If I worked in a team as experienced and knowledgeable as me, my feedback would have less value. I could also easily imagine some managers making the number of reviews an empty metric that had to be tediously gamed, much like green squares on GitHub.

Is it more common than not that senior engineers aren't appropriately rewarded for investing time in code review? Probably, most companies are imperfect in one way or another.

I'm viewing it from Ireland, and half way down the page, I see a full-screen banner for Disney+ with a notable personality from each of their franchises Moana (Disney), Mr Incredible (Pixar), Thor (Marvel), Jyn Erso (Rogue One/Star Wars) and Jeff Goldblum (National Geographic). I suppose that's what you're seeing?

I saw a production of Ulysses twice in the Abbey Theatre in Dublin on two separate runs. I had already read the book, but seeing it performed was a completely different experience, like seeing a Shakespeare text performed in film or on stage. Similarly, I saw an adaptation of the Cyclops episode in the New Theatre, which was incredible. I know Ulysses is unfilmable, but I'd like to see someone like Paul Thomas Anderson try.

The audiobook, narrated by Jim Norton, is also great. His delivery is quite engaging, and any parts that might be a bit impenetrable while reading flow over you, and you can hook back in later.

I understand the rationale behind using the native constructs of JavaScript as much as possible, but this is where I feel Solid.js made a reasonable compromise to pragmatism. There are JSX constructs for conditions and looping, making certain things easier or clearer to express.

If the people don't exist, they can't produce. You can make all the policy decisions you want, but the economy will stagnate if you don't have people working in fields or factories or wiring up houses. Sure, better education might make higher-value workers that produce more economic value. Providing better support for families will help people interested in having children potentially have more children and be economically productive while doing so. If your current citizens don't want to have children, then it doesn't matter.

It's helping Germany offset an ageing population and declining economic productivity. If age distribution in your population is becoming unbalanced and you can't encourage the current residents to increase the birth rate, what other option is there?

https://www.reuters.com/world/europe/migration-drives-german...

I think one of the biggest benefits, which I rarely see mentioned, is that all the class names are shared. When building your CSS for production, you can look at the classes you use and only add them to your CSS bundle. If you remove a class from somewhere in your HTML, the associated CSS gets dropped from your bundle. Your output CSS will shrink or grow with the classes that you use. Typically it's harder to remove dead CSS from traditional codebases.

Because the classes are shared to begin, there is less redundancy in the final CSS than using custom classes, perhaps with mixins to do standard flex or positioning patterns. So the resulting CSS file is typically relatively small and kept small by the dead code elimination. You can ship the entire CSS file to any page or on the initial page load for a SPA and not worry about code splitting your CSS, which can be troublesome in some builds.

This is technically true if you go out and start running a lot from zero if you are overweight or ignore your body and the warnings it gives in the run-up to injury. If you build up running gradually and treat it as a skill that you learn and improve on your technique and always listen to the feedback your body is giving you, then running is a great way to improve the health of the joints, muscles and bones in your legs and feet.

Most children happily run around all day and rarely develop any issues. Adults have an unfortunate habit of becoming quite sedentary, losing any conditioning they had and then going out and running distances their body isn't prepared for. Then people will blame their shoes or even the activity itself when the most significant factor is doing too much too soon.

This interview with Daniel Lieberman[1], an evolutionary biologist out of Harvard, is a good read about the misconceptions associated with human activity and what studies of our historical behaviour can tell us about what is and isn't important in staying active.

https://news.harvard.edu/gazette/story/2021/01/daniel-lieber...

You also don't need the mat, also known as the pellicle, to start brewing kombucha. It is entirely redundant. Just get a couple of bottles of unpasteurised, unflavoured kombucha and use that as your starter, along with the fresh tea and sugar. Those kombucha starter kits with a pellicle are just a big scam.

Ain't that the truth? So much folklore and superstition about how the fermentation process works. I remember being told you can't make Jun with a Kombucha starter because it's a different bacteria, and even if you did get Kombucha to ferment the honey, it wouldn't actually be Jun. And the complete obsession and misinformation around the pellicle!

It is geared toward people who want an inexpensive, convenient meal that theoretically contains all the nutrients you need. Some people use it as an alternative to breakfast or lunch, and some people are all in as a complete meal replacement because they don't really care about the experience of eating that much. The founder says he uses Soylent for most of his daily nutrition but will still eat out with friends. The people who use it for a complete meal replacement talk about how they have to chew gum. Otherwise, they get muscular dystrophy in their jaw.

I see the benefit of it as a convenient breakfast or lunch. I like food too much to replace all my meals with it.

I used to work for an automated property valuation platform. It was basically a property valuation workflow tool that presented valuers with the right data at the right time so they could drastically reduce the amount of time spent valuing each property and theoretically produce much more accurate results.

We spent so much time working on features and workflows to interact with clients rather than building the platform for our actual users, the valuers. We could have picked any CRM off the shelf, adopted its way of working, and saved ourselves a lot of time. There is no scenario in which the CRM subscription would have exceeded the cost of the developer's time to produce the cobbled-together half-baked solution we ended up with.

Minor correction, Svelte dispenses with the Virtual DOM an algorithm for making DOM updates, not the Shadow DOM which is a completely separate browser construct for isolating subtrees in the DOM.

Or there is Inferno which is VDOM based and outperforms Svelte on most benchmarks. The whole narrative of "VDOM is pure overhead" doesn't hold out in practice, and I suspect really just an excuse to attack React and promote Svelte.

https://krausest.github.io/js-framework-benchmark/2023/table...

We used to listen to that 3 CD box set on family driving holidays when I was a child. We get the ferry from Dublin, drive through the UK, get the Eurotunnel to Calais and then head wherever, though usually, we end up in Italy. I remember in school, I was singing under my breath, "I just don't know what to do with myself", and a classmate demanded, "How do you know that song?". I just shrugged, and it was only a bit later that I became aware of The White Stripes cover of the Chuck Jackson original that had just come out.

Those songs, along with Sgt. Peppers, Abbey Road and the few other albums that fit in our CD case are ingrained in my memories from that time. We'd rotate stuff in and out from year to year, but Bacharach and The Beatles always stayed in.

I think the site looks grand. One suggestion would be to make your card background white rather than yellow. I think it would help with contrast against the background of the site and make the text easier to read. Other than that you have your opening times, your menu and your location, and it's all front and centre. The only thing I'd add is a map to make your location easier to find but that's not a huge deal.

If a student can look up anything on ChatGPT it could very well inhibit their ability to develop critical thinking skills. They could just copy the output of ChatGPT rather than actually engaging with a text like Of Mice and Men, for example, and considering what it's trying to say about the American dream or interpersonal connections. Lots of learning exercises are relatively meaningless in isolation but are a part of a greater skill development journey. It's like just taking the answers from the back of the book rather than working through exercises. Getting the answer isn't the point. The point is actually doing the work so you develop skills that can be used beyond your current homework assignment or exam.

This could have been a year ago at this stage. It was on r/svelte, if I recall correctly. Svelte doesn't have idioms for reusable reactive logic. The $ sign is used to drive functionality in Svelte, so you can't use it to signify something observable like with RXJS. For Solid, they use createQuery because that is the convention in Solid. For Vue and Svelte, they stick with useQuery. I think the idea is that useX is just a shorthand for "here is some abstracted reactive functionality". Ultimately it has nothing to do with how the reactivity works, it just says, "this function will tie into your reactivity". They could have just called it query, but it seems arbitrary to change the name.

I'm primarily a React user and would generally agree with you, but I understand why people like Vue/Svelte.

- Templating languages have been around for years, and for many, they feel like the right way to write markup. If someone has used Handlebars in the past, the templating constructs feel familiar. There is also the idea of keeping logic out of your views with the restricted feature set of your templating language. Finally, conditional logic is simply easier in a templating language vs JSX. This will be true until we get pattern matching or the do expression, ternaries, and boolean expressions are clunky. Solid added constructs for conditions and looping to JSX, mainly for performance, but it's much more ergonomic.

- People like the SFC pattern precisely because everything is separate. Your logic is separate from your markup, which is separate from your styling. For me, it feels like a throwback to the times of MVC when it was good and proper to separate your concerns that way. Some reject React out of hand because "there's no default solution for styling".

- The composition API in Vue 3 and Svelte's stores provide the same abstraction potential as hooks. Their reactive primitives aren't tied to the component lifecycle, which is a really nice benefit. It avoids a lot of the context performance pain that people can end up in.

Overall, I'm not really sold on SFCs. They inherently limit you to one component per file, a tradeoff I don't like. There are also the type and IDE support issues which will always be an uphill battle. Template languages are at least better than lashing everything in template strings which is becoming a thing now.

It's funny; I often see it the opposite way. Passing components as props enables inversion of control and usually helps split responsibilities up more easily and generally avoids prop drilling or super components that do everything.

Solid does have state management. Its state management primitives can be used outside components and can even be used completely on their own, and its stores are fairly similar to Svelte stores.

https://www.solidjs.com/docs/latest/api#stores

I find a lot of Svelte users are pretty religious and hysterically anti-React. When the first version of Svelte Query was announced, people were trashing the API because it looked like hooks and "you don't need those in Svelte", concluding the library must be useless. There's a lot of the "Svelte is the one true way" talk, similar to when Vue was the main alternative to React. The core team seem very reasonable but I think the community has some maturing to do.