why are there so many "it is so hard to get a job everything sucks" posts

many of them don't even read as if they are written by a human? and often have kind of wild takes?

despite it literally being a lifelong passion and the thing i am probably best at, i felt incredibly dissuaded from this field by such posts and comments earlier this year. i'm thankful that i got over this, because i persisted and now have offers for the summer. perhaps this is survivorship bias but i really do not feel like my peers in commerce or other degrees are having an easier time in their respective job markets.

also: haven't we learnt that the government or media saying "we need more jobs in this area" is often not at all reflective of how easy it is to get into said area? jobs change, job markets change. taking a gamble and spending additional years training to become an electrician or hvac technician because it is 'in demand' does not seem wise at all. it does not seem to be all sunshine and roses in trades, either.

outside of reddit doomerism, it is hard to find people that truly believe that despite computing set to be an even bigger part of our lives, having people who understand software or computers on some level is completely worthless.

if you are young and passionate, i think you should absolutely pursue cs. ai or not, "computers being economically valuable" seems an unbelievably safe bet. the idea that humans won't capture *any* of that value seems pretty crazy to me.

call me an optimist or a sweet summer child, but this widely held doomerism does not seem justified at all. and where there are widespread irrational views, there are generational opportunities to act on (what you believe) to be a slightly more correct vision of the future. im super excited about the next generation of au/nz tech!

reddit.com

u/Juiced_ — 1 day ago

▲ 139 r/typst

Releasing typst-wasm and vite-plugin-typst

hello folks

today i am pleased to be releasing typst-wasm and an experimental version of vite-plugin-typst!

the goal of this project is to provide a pragmatic promise based API for compiling typst using wasm in as many runtimes as possible.

the api is consistent across all supported runtimes and closely mirrors what you see in the rust crate. it gives you full control over where and how you load the wasm blobs, which allows you to provide the best possible user experience.

running typst in wasm/serverless environments like cloudflare workers or vercel allows you to do SSR, easily offload compilation to the server for low bandwidth devices while reusing code, run typst in sandboxes for AI agents, etc.

here's an example of the API:

await compiler.addFonts(
  readFile(new URL(import.meta.resolve(
    "@typst-wasm/fonts/NewCMMath-Regular.otf",
  ))),
);

await compiler.addSource("main.typ", "= Hello from typst-wasm!");
const result = await compiler.compile({
  main: "main.typ",
  format: "svg",
});

console.log(result.pages[0]?.output);

how does it differ from typst.ts?

the goals are different! typst-wasm aims to support many runtimes and provide a consistent api without the use of deprecated APIs.

@typst-wasm/vite-plugin-typst

I am also releasing vite-plugin-typst, built on typst-wasm, to provide an easy way to use the new html output in your vite apps! to give you ideas, this is a cool alternative to markdown for content in vite-based websites/blogs!

import typstDocument from "./post.typ?typst=html";

document.querySelector("#output")!.innerHTML = typstDocument.html;

u/Juiced_

why are there so many "it is so hard to get a job everything sucks" posts

Releasing typst-wasm and vite-plugin-typst

how does it differ from typst.ts?

@typst-wasm/vite-plugin-typst

links

Why do the new Myki readers update or load parameters so often?