HN user

RobbieGM

60 karma
Posts4
Comments30
View on HN

I took this course 3 years ago. I found it fast-moving, and it focused a lot more on applications than fundamentals, which meant it was more wide than it was deep. This didn't turn out so well when I decided to study ML later and needed stronger linear algebra fundamentals, but it was a fun course. There were a couple interesting course projects, one of which was using linear algebra to balance a (simulated) 2D robot.

  Location: Ann Arbor, MI
  Remote: Yes, or hybrid/in-office
  Willing to relocate: Maybe
  Technologies: JavaScript/TypeScript, C++, Python, Java, Git, React, Next.js, Node.js HTML, CSS, SQL
  Résumé/CV: https://robbiegm.github.io/ https://www.linkedin.com/in/robbie-moore-7217b9175/ (resume with references available upon request to protect their privacy)
  Email: robbiegm@umich.edu
I'm a University of Michigan 3rd year undergrad student looking for a summer 2024 internship. I fell in love with programming 9 years ago, and have been aiming to make maintainable, user-friendly software ever since. Outside of school, I've built my programming skills by creating a number of side projects, working freelance, and doing two summer-long full-time internships at Domino's. At the University of Michigan, I've taken courses covering machine learning, robotics, computer microarchitecture, data structures & algorithms, technical communication, and more.

Do you have a more sustainable way to produce meat in mind? Ethics aside, the addition of another trophic level makes meat production necessarily less efficient than that of an equivalent amount of plants.

For anyone interested in trying it know there is one major downside: most Linux binaries won't run on it because dynamically linked libraries work strangely on NixOS

If you then distribute that modified software, users don't have the freedom to modify it in turn since your source code would be unavailable.

Almost nobody is doing this, and almost nobody ever will because it breaks accessibility and a whole host of other features. I would save the alarmism for another day.

"Do it in a browser" is not interesting enough.

I disagree. DAWs are huge pieces of software to begin with and doing high-performance audio work in the browser would be very impressive.

An SPA Alternative 4 years ago

Without any real restrictions? JavaScript is very restricted in what it can do. Most APIs that you'd expect to be gated behind a permission are gated behind a permission.

Snapchat for Web 4 years ago

Sure, but can it be done in software, or will it require a scanning tunneling microscope?

That difference is what I'd be interested in anyway as a developer who focuses on PWAs (where the cost of chrome is paid for already). I'm trying to work out whether a WASM stack would help runtime performance, memory usage, and startup time, but based on these numbers it doesn't look so inspiring.

I get that it would have a startup cost but I'm shocked that it uses more memory. Everyone complains about what a memory hog electron apps are and I assumed it was because of JS. But maybe we need something other than micro benchmarks to compare.

He makes a point of showing how hard it is to achieve the same performance as JS with wasm, but the majority of the problems he runs into are AssemblyScript-related. Also he doesn't mention that wasm is faster to parse than JS. I'd be interested in a comparison of JS and wasm from the POV of a UI-heavy, compute-light app.

I don't mean to take a crap on this creation, but it really paints PWAs in a poor light by itself being a bad one:

- Animations are janky because they use CSS properties which trigger more than just the compositor

- Carousel cannot be navigated by scrolling left/right on desktop, or by clicking the small circles below

- Almost all UI text is selectable

- Common keyboard shortcuts (esc to close modals, for example) don't do what I'd hope

- Search page results are one tile wide regardless of available screen space

- Uses a bottom navigation bar on desktop (ok, I'm guilty of this one too)

- UI changes from the bottom navbar wait on the network (usually a characteristic of normal websites, not native apps or PWAs)

We have a ways to go before PWAs can become mainstream.