trying to figure out why this shit is happening. it seems to be due to an old version of @vueuse/core I think???

[INVALID_ANNOTATION] A comment "/* #__PURE__ */" in "node_modules/.pnpm/@vueuse+core@14.3.0_vue@3.5.39_typescript@6.0.3_/node_modules/@vueuse/core/dist/index.js" contains an annotation that Rolldown cannot interpret due to the position of the comment.
      ╭─[ node_modules/.pnpm/@vueuse+core@14.3.0_vue@3.5.39_typescript@6.0.3_/node_modules/@vueuse/core/dist/index.js:3362:1 ]
      │
 3362 │ /* #__PURE__ */
      │ ───────┬───────
      │        ╰───────── comment ignored due to position
      │
      │ Help: For more information on how to use pure annotations correctly, check the documentation: https://rolldown.rs/in-depth/dead-code-elimination#pure
──────╯

but I cannot figure out how to UPDATE that old fucking version of @vueuse/core.

$ find . -iname @vueuse
./node_modules/@vueuse
./node_modules/.pnpm/node_modules/@vueuse
./node_modules/.pnpm/@vueuse+integrations@14.3.0_axios@1.18.1_change-case@5.4.4_vue@3.5.39_typescript@6.0.3_/node_modules/@vueuse
./node_modules/.pnpm/@vueuse+metadata@14.3.0/node_modules/@vueuse
./node_modules/.pnpm/@vueuse+core@14.3.0_vue@3.5.39_typescript@6.0.3_/node_modules/@vueuse
./node_modules/.pnpm/reka-ui@2.10.1_vue@3.5.39_typescript@6.0.3_/node_modules/@vueuse
./node_modules/.pnpm/@vueuse+shared@14.3.0_vue@3.5.39_typescript@6.0.3_/node_modules/@vueuse

fucking amazing.

I have a js project with

tailwind.config.js
components.json
package.json
tsconfig.app.json
tsconfig.json
tsconfig.node.json
eslint.config.ts
playwright.config.ts
postcss.config.ts
unocss.config.ts
vite.config.ts
vitest.config.ts
pnpm-lock.yaml
pnpm-workspace.yaml

why is the js ecosystem like this?
I fucking hate js.

there is NO reason for your repository to have THIS many config files in the root directory.

with gradle, here are the files I have in the root directory (excluding README.md, LICENSE, CONTRIBUTING.md, .gitignore, .editorconfig, etc.):

gradlew.bat
build.gradle.kts
settings.gradle.kts
gradle.properties
gradlew

and THAT'S IT

eslint.config.js
netlify.toml
package.json
pnpm-lock.yaml
pnpm-workspace.yaml
taze.config.ts
tsconfig.json
tsdown.config.ts
turbo.json
unocss.config.ts
vitest.config.ts

mental illness.

every time I need to engage with it, it makes me want to rip my hair out

I fucking hate the js ecosystem so much

"why the fuck did my build break and suddenly sharp can't convert images to JXL even though it could do that perfectly fine before??"
>spend 30 minutes looking into it
>they removed the postinstall script
>now if you want to use a global version of libvips you need to cd into the node_modules directory and manually run the build script

the fuck are they smoking

I FUCKING HATE STALE BOTS

https://github.com/parcel-bundler/parcel/issues/9929

$30 -> $300 for 10GB worth of memory chips (half shipment in 2027, half shipment in 2031) is fucking INSANE

https://youtu.be/7f2BjPPJEWg

RCE Exploit in Litematica for 1.21+

Litematica file versions for 1.21+ have been found to contain a Remote Code Execution Exploit, allowing malicious code to be executed on your computer in multiplayer servers (Does not include singleplayer worlds).

Get more info's from here:

https://www.reddit.com/r/litematica/comments/1up8uqk/important_announcement_litematica_vulnerability/

#ModdedMinecraft #Minecraft #Litematica

"every time i meet a mechanical engineer the quality of their work seems to relate in a generally proportional manner to how badly they wish they could fuck the machine"

"watch my videos on spotify"

shut up

by "incremental", I mean "it only recompiles the function that changed and not the entire TU"

why can't they just make an incremental C++ compiler?

like, other languages do this, so why can't C++?

they should invent a colcon that doesn't make me want to strangle someone

wtf, the bool type and true & false only became keywords in C23???

@solonovamax I heard of someone saying what two professors believed AI is good for. One was an English major and the other an Artist.

The English professor stated that it can't be used for writing words because it doesn't understand nuance, but for something simpler "like art" it can be used for that.

The Artist professor simply stated the same thing, just that Art can't be generated but English can be.

The AI is good at being average. For people who are less than average at doing something, AI would be the thing they use. But like the studies show, you can't be better than average when you use AI tools.

it most definitely takes creativity

a different kind of creativity, sure, but creativity nonetheless

"coding isn't art!!! it doesn't take creativity!!!!"

fuck you, shut the fuck up and don't come back until you've spent 20+ hours toiling over the ideal way to design something to solve a problem and then throwing it all out and rewriting it from scratch