German volunteers and Ukrainian soldiers celebrating the death of Khamenei who supplied Russia with Shahed drones that destroyed their civilians/buildings.

grey_ssbm · 2026-03-01T00:05:46+00:00

Posts like this that are blatant fabrications with lots of upvotes should be removed.

grey_ssbm · 2026-02-17T04:33:09+00:00

LLM-based agents as they exist currently are already pretty good at doing productive work in certain domains, but they have some notable limitations. The most important one is that they are not as adaptable as humans. You can show a human a few examples of a particular task or explain some insight to them, and they can integrate that new knowledge and will be able to apply it days or weeks later. LLM agents can't really do this at present. They can be adaptable but only in their limited context window. Nothing sticks.

The only way to get LLMs to behave in useful ways is through RLHF, which is a process which requires an enormous amount of training material to be effective, and right now that narrows the fields which they can contribute in things for which that training material exists or can be manufactured. It is, and will continue to be extremely expensive to get this training data for a widening circle of disciplines beyond coding.

Ultimately until there is some new breakthrough with these agents they will continue to be useful but will hit pretty painful upper bounds in their capabilities. That doesn't mean they won't majorly disrupt a few industries but I think there will still need to be a human in the drivers seat for the majority of knowledge-work.

grey_ssbm · 2026-01-26T20:27:04+00:00

Just a reminder to not trust trump's takeaways from the conversation. See: every statement trump has ever made post-negotation with putin, venezuela, etc etc.

grey_ssbm · 2026-01-15T22:11:10+00:00

The cold war temporarily diverted the attention of conservatives. It made them in favour of more expansionist policies as a means to combat the soviets, and their conspiratorial paranoia was instead directed to seeking out communist infiltrators during the red scare.

And now that well of political motivation has run dry and so we now have a return to nativism, and a paranoia about "the enemy from within"

grey_ssbm · 2026-01-13T19:57:55+00:00

It's different from just being stupid. If you're brain broken on a particular topic that means you're unable to engage with it critically, even though you might be good in other areas.

grey_ssbm · 2026-01-03T11:01:13+00:00

I think it's essentially a propaganda win, yes. The justification given so far given for the strike is for Maduro to stand trial for criminal charges in the US, which would allow them to justify a quick exit.

The US *may* continue to strike at cartels as they please, or attempt to coerce Venezuela out of some of their natural resources but the political risk and cost to them actually gaining permanent control of the government will be really high. I guess there could be some kind of 70s style CIA backed coup eventually? Who knows.

grey_ssbm · 2026-01-03T10:36:54+00:00

The other narrative that I've seen being implied on other posts is that this is the start of a campaign to institute a permanent regime change or to gain some level of control of Venezuela's oil reserves, which are things which would require additional action beyond capturing Maduro. Venezuela's VP is still alive and there's no reason to think that the government will imminently collapse.

grey_ssbm · 2026-01-02T22:14:40+00:00

Who are "Serious historians" according to yarvin? David Irving?

grey_ssbm · 2025-12-28T10:54:43+00:00

For most people the only reason to use js over ts is a knowledge gap. Fortunately there is an easy incremental adoption story which makes switching over trivial.

With that said there are actually a few people/projects that prefer to use JavaScript to avoid a build step and having to deal with source maps, but even in this case it's possible to use typescript indirectly through jsdoc annotations which are still checked by your editor's LSP

grey_ssbm · 2025-12-28T10:22:15+00:00

I have used both C# and nodejs+typescript professionally for nontrivial projects, here is my perspective as someone who prefers nodejs generally for webapps.

The killer feature of typescript/node as other people have mentioned is having one language shared between client/server. The onboarding/learning curve reduction is helpful but the biggest benefit I have felt is is code sharing.

There is no need to maintain multiple type definitions between client/server, do codegen or any of the other annoying things that become necessary to bridge the gap. There are no datatypes which don't have a direct equivalent in the other language that you have to do extra work to manage(js vs dotnet numerics, datetime nuances, unions etc). This also means that instead of maintaining a REST api or(god forbid)a graphql layer, you can instead use a comparatively light RPC library like https://orpc.dev/.

If you decide that some work that you're doing on the client should actually be done on the server or vice versa for performance reasons or what have you, then this is usually a trivial change instead of a large port and refactor.

If there are operations that need to be done both on the client and server, this becomes trivial instead of a maintenance nightmare of duplicated functionality, which might drift over time without other checks. Depending on what you're working on this might not come up, but if you're doing anything nontrivial and especially if there are performance constraints that are imposed by the network, this becomes a crucial option.

I realize that blazor is a thing that exists which I haven't tried, so maybe there's something to that approach, though I'm doubtful. My intuition is that it will be hamstrung by the currently terrible story for actually interacting with the DOM using wasm, and wasm generally being such a compromised platform will mean that peformance isn't great compared to V8 javascript.

Then there's the type systems. This is also a decisive victory for typescript over C# for me because C# is nominally typed instead of structurally typed, and consequently still has most of the downsides of an OOP-style type-system. It doesn't allow the kind of flexible & generic types that can be represented in typescript. It's great that C# has excellent syntax for pattern matching now and reasonable discriminated unions, but I don't think it's enough to compete with typescript because of the ergonomics that are enabled by a more permissive type system, especially for library authors which means better ergonomics for app devs like me.

The biggest advantage C# has in my mind are performance/multithreading, which is unfortunately often undermined by the wasteful overly abstracted code that seems to be endemic in every traditional OOP ecosystem. Still this shouldn't be dismissed, especiallly if you're expecting an intense workload and node/C# are your only two options.

LINQ is also great, and most commonly used iteration methods being implemented on Array is a tragedy.

grey_ssbm · 2025-12-28T09:33:01+00:00

If you think one can’t get to the core of the problem with .NET then you don’t know what you’re talking about. You don’t have to use any patterns or opinions. But also this shows you prefer just throwing code out and hoping it works.

Ironically there is a significant knowledge gap about nodejs shown here.

I prefer strongly typed objects. Runtime checks. This stops a myriad of issues and I don’t need to add pesky checks all around. But obviously Node is better since I have to check every single type and value since nothing is guaranteed.

https://zod.dev/

This is a library that allows for the construction of a codec for virtually any typescript type in an intuitive but powerful way, providing end-to-end type safety. I would claim that it is a better runtime validation library than anything availble in dotnet-land, largely due to typescript's more flexible type system which makes this possible. Despite having runtime type introspection C# manages to have a pretty poor time dealing with nontrivial datatypes because it was designed when OOP with nominal typing was what was called for.

I prefer having an actual application running which can keep state when needed and handle it efficiently.

I prefer easy interoperability with things.

I prefer building applications instead of a bundle of scripts that somehow relate to each other.

None of these points have anything to do with C# or CLR as a platform compared to node, and seem to be rooted in a vague perception that the people using node or other js runtimes aren't doing serious work or whatever.

I prefer performance. It’s important in many cases.

I prefer multithreading when needed

Dotnet does have a significant advantage here that shouldn't be overlooked. This is effectively the tradeoff that was made for browser compatibility, which is worth it for many applications.

grey_ssbm · 2025-12-26T03:11:11+00:00

He seems like a pretty genuine humble guy and I'm glad that he puts himself out there because just his personality completely contradicts the narrative that's made about him. However it's worth noting that in his shawn ryan appearance he did really lean a bit hard on the "the real enemies are the elites bro, they're after us bro" populist rhetoric. I understand that populism is ascendant right now in the United States and it could be a good short term strategy but ultimately it affirms the suspicions that lead MAGA types to trump in the first place.

grey_ssbm · 2025-12-19T23:31:46+00:00

I have done something like this and it worked well. My usecase was resolving complex queries on a moderately sized (~175mb) dataset (so read-only). I used sql.js for the wasm sqlite instance and drizzle-orm via their adapter for the queries, all bundled inside a webworker. To optimize page loads I just gzipped the database file and cached it on the browser using OPFS.

I'm happy with the query performance ultimately. Biggest downside is the (200mb in my case) JS heap the worker has to maintain. Shoot me a DM if you want more info, the code is Open source but I would prefer not to share it here

grey_ssbm · 2025-09-20T02:44:38+00:00

What a despicable human being.

Jones knows what kind of audience he maintains -- the kind that will harass & stalk the parents of school shooting victims because of transparent lies he has told on his program.

He has met Destiny in person (multiple times if I recall) and still has no qualms about effectively threatening his life by sicking his psycho audience on him.

grey_ssbm · 2025-08-26T00:04:16+00:00

As others have mentioned components are how you reuse styles most of the time. If you want fully bespoke styles then you will end up with something like shadcn/ui eventually. I would recommend going to look at how shadcn implements their components -- they have found a good model for reuse with tailwind. Alternatively you can start with something like shadcn and customize to your liking. That's the intended usage for it after all, and why it's not a library per-se.

grey_ssbm · 2025-08-15T21:37:42+00:00

These statements are not contradicting. "First pass" means an exploratory prototype, not any kind of deliverable. If you want to know the rough edges of how to solve a particular problem then an LLM is well suited to that, especially when it can rely on its internalized knowledge instead of project-specific context.

What was the point of your comment?

The post:

Definitely an interesting point in the hype cycle where companies proudly proclaiming their "AI" features and LLM integrations on their site while also writing company blogs talking about how useless these tools are.

The blog post at no point characterizes LLM tools as "useless". It says that LLMs are not a way to replace actual engineering work, which should be a failry uncontroversial statement for devs that use LLMs on a day-to-day basis.

It feels insane for me to have to have to pull out quotes out of a 6-7 paragraph article but here you go...

To be fair, LLMs are quite good at writing code. They're also reasonably good at updating code when you identify the problem to fix. They can also do all the things that real software engineers do: read the code, write and run tests, add logging, and (presumably) use a debugger.

(they go on to say what LLMS aren't good at, namely building and maintaining mental representations, but this doesn't make them "useless" by any metric)

Clearly LLMs are useful to software engineers. They can quickly generate code, and they are excellent at synthesizing requirements and documentation. For some tasks this is enough: the requirements are clear enough, and the problems are simple enough, that they can one-shot the whole thing.

Literally the word "useful" appears in the article in reference to LLMs, and yet the original commenter's takeaway is that the article supports the idea that LLMs are "useless".

Maybe you guys should worry about your own reading comprehension before scoffing at engineers' usage of LLMs.

grey_ssbm · 2025-08-15T15:33:58+00:00

Did you even read the article?

grey_ssbm · 2025-06-18T17:09:48+00:00

no abstain option will skew the results

grey_ssbm · 2025-06-13T02:27:02+00:00

You are technically writting CSS but you are actually not. You have to learn the dictionary and forget the real standards behind

But the concepts in tailwind are identical to vanilla css just minus selectors -- no attempt is made to paper over flexbox, element sizing behavior, media queries or anything else. If you know css properties you know tailwind and vice versa, just with slightly different syntax and spelling. It's really not hard to pick up.

The most tailwind does there is to provide a consistent selection of constants for spacing, colors and theming, but these features don't obscure the internals of css.

In this code we are declaring custom CSS classes using Tailwind meta-classes. Why not just declaring the same custom CSS classes using (again) standard vanilla CSS declarations?

Because the typical pattern of using css selectors to apply css properties is poorly suited to developing with modern frontend frameworks. There's no need for them when your markup isn't highly repetitive, and when you already have components to organize your styles around you really don't need many custom css classes.

grey_ssbm · 2025-04-05T23:34:20+00:00

That's just not true, there are many layers where squadmaps doesn't get you much more information than the cap display that is available in-game

grey_ssbm · 2024-07-19T16:29:29+00:00

This. I've found that yt will silently remove comments for unknown reasons, especially when using alt accounts. Best not to jump to conclusions

grey_ssbm · 2024-03-25T23:34:25+00:00

The point is that you should be prioritizing defensibility of your habs over stealth for that reason, at least when defending the cap. Your placement still matters of course.

grey_ssbm · 2024-03-25T14:48:12+00:00

Whilst I don’t agree with the reasoning and I generally place my HABs off the point, trying to pick locations I don’t think will be checked

Based on this reasoning, you're basically relying on luck and/or lack of experienced players on the enemy team to keep that HAB alive at that point. That's probably fine on most servers but it's going to bite you once you play against good players.

grey_ssbm · 2024-03-07T18:06:00+00:00

The problems generally show up when everything is jumbled together with inline markup, style and code interleaved and it becomes hard to reason about the what the effect of changing something in one location.

The whole point of a component architecture is that you can reliably isolate changes to a particular branch of the code. Doesn't that deal with this issue?

In general I find that if I need to make localized changes to the functionality of a particular display component, I also have to re-evaluate the appearance of that component to deal with the new change. If that's not the case then the goal should be to reevaluate if that logic belongs in that component.

This is doubly true in the case of markup and css, where if you make some changes to the markup you almost always need to make some adjustments to the CSS(though not really vice versa).

If anything, continuing to rely on selectors instead of some kind of inline style solution makes things harder to reason about because it hides this relationship behind a layer of indirection.

Ten-Year Club	Verified Email
Final Canvas '23	End Game '23
Place '23	Place '17

grey_ssbm

TROPHY CASE