I thought the same and felt it looked really out of place to have I8 and F32 instead of i8 and f32 when so much else looks just like Rust. Especially when the rest of the types are all lower case.
Agreed, that really stood out as a ... questionable design decision, and felt extremely un-ergonomic which seems to go against the stated goals of the language.
Every language is apparently required to make one specific version of these totally arbitrary choices, like whether to call the keyword function, func, fun, fn, or def. Once they do, it’s a foolish inconsistency with everything else. What if the language supported every syntax?
I really enjoy the website content and appreciate the hard work to create it. Also, thank you to the author for taking action on the HN feedback last year about the AI thumbnails that used to be all over this site. [0]
I would say the spirit of a jam is to start from scratch, but using parts and techniques you're used to is fine. e.g. repurpose your number parser but not the entire grammar and runtime. A lot of being successful at a jam is doing the right prep work so you're not making decisions and figuring things out at jam time.
Certainly, it is full of algorithms, but that's not what this book is about. This book is about possibilities. Its purpose is to present you not only with the prerequisite mandatory knowledge of the available problem-solving techniques, but more importantly to expand your ability to frame new problems and to think creatively.
I'm still wondering how people find emojis to insert into their texts. Do they scan the list of emojis to find something suitable for each place in the text? Or maybe they memorized a lot of emojis, they know they exist and it is sort of automatic: you write text and the idea pops up to insert an emoji that I discovered some time ago?
I hope that it is closer to the latter, because I'd kill myself if I was forced to look for emojis so much. From other hand to memorize dozens (hundreds?) of different emojis doesn't seem fun either.
I think you may be in the vast minority here. People born after 1990 grew up using emoji and most keyboards show your top ~25 most used emojis, floated to the top, and keyboards offer search function, this was a largely solved problem by 2014, over a decade ago.
Ah. I see. I replace the virtual keyboad on Android with something else instantly, to get rid of autocorrect and other anti-features. Probably doing that I lose my chance to appreciate the ways of people born after 1990.
Sorry if I'm misunderstanding, but isn't FEM used in physics engines because it is an good approximation for the underlying physics? For example, I believe the Drake Physics engine uses FEM to model deformable materials relating to vehicle crashes at Toyota
FEM is just a numerical technique for solving some kinds of differential equations. It doesn't aitomatically make you accurate or not, just like any other stable solver.
The commenter says pre-rendered/server-side-rendered mathematics (via katex) is great - I’ve found the opposite. It’s probably great if you have an article with one or two equations. On the other hand, if you have an article which uses mathematics pervasively, like many pure mathematics articles, it quickly becomes far more space efficient to render the mathematics on the client side. You can quickly get 200kB+ pages by pre-rendering.
My experience with dynamically rendered math has been the opposite: if you have lots of equations to render, it inevitably takes some milliseconds to render, which makes the whole content move around and shake as rendering takes places.
Of course, if the page uses more symbols in various sizes, then a few more fonts files (.woff2) need to be pulled in which case the weight of KaTeX would increase a bit too. Each font file weighs between 4 kB and 28 kB.
