Rik Arends

@rikarends

Building Makepad, Livecoding for Rust for native and web

Amsterdam
Joined July 2009

Tweets

You blocked @rikarends

Are you sure you want to view these Tweets? Viewing Tweets won't unblock @rikarends

  1. 18 hours ago

    Seems most likely everyone will do WSL and keep a WSL->Spirv compiler tucked away somewhere.

    Show this thread
    Undo
  2. 18 hours ago

    Reading up on webGPU, looks like its headed towards a Spir-V vs WSL face-off. Great. I strongly prefer WSL since its easier to write cross compilers for, but the rest of the world likes spir-v because of existing compiler stacks. Now we'll get to do both, grreat.

    Show this thread
    Undo
  3. Feb 1

    In some sense its similar to that mario64 code. Every single bit of that game experience you love is written out in If's and action statemachines and spawning graphic elements. By hand, by someone.

    Show this thread
    Undo
  4. Feb 1

    UI complexity has an irreducibility to it. You can jump high, low, make frameworks, make everything a new language, invent DSLs, you will not escape it. Behavior will be encoded somewhere and if you build UI's, you have to do it.

    Show this thread
    Undo
  5. Feb 1

    Just because i made building complex widgets as nice as i possibly could, doesn't mean building complex widgets isn't extremely hard still.

    Show this thread
    Undo
  6. Feb 1

    Even though i've built makepad all this way up to get just here. But you also realise how far i still am from where i want to go.

    Show this thread
    Undo
  7. Feb 1

    Right now writing tokenstream diffing so the editor can recognise the live-macros, parse them and hot update them in the running program. But i'm not very motivated for some reason, therefore i tweet :)

    Show this thread
    Undo
  8. Feb 1

    Another thing is if you work for small companies/startups and yr a highly skilled/specialised dev, very often the math doesn't work out. The small company can't actually afford you so they have no hope to replace you if you leave.

    Show this thread
    Undo
  9. Feb 1

    Of course this highly matters if you are a programmer in a differentiable space. Plumbing java ORMs? Here's a whole can of people to replace you. However if you are fully specialised and maximally tech leveraged, not so much. They couldn't hire to replace you remotely easily.

    Show this thread
    Undo
  10. Feb 1

    I suspect a lot of cleanup/repair yt videos to be complete fabrications. Some dirty/bad things just look like they've been rapid-rusted or just spraypainted with foodcoloring.

    Undo
  11. Feb 1

    If you look at a basic JS UI from a systems point of view the 'total system complexity' becomes absurd. Megabytes of JS on top of a JS engine on top of a 'nobody knows how it works' CSS engine and render engine. Thats a LOT for a todolist or a button.

    Show this thread
    Undo
  12. Feb 1

    What it took for me to figure it out is building code-editors. Anything out of the primary usecase-flow of HTML and you learn its a very domain specific renderstack.

    Show this thread
    Undo
  13. Feb 1

    Its inpredictable, buggy, slow. Yes it has nice fontrendering, have to give it that.

    Show this thread
    Undo
  14. Feb 1

    This idea that HTML is somehow nice for UI's isn't actually true.

    Show this thread
    Undo
  15. Retweeted
    Jan 28

    Amazingly, Super Mario 64's C code wasn't compiled with compiler optimizations enabled: This helped fans decompile the game into C:

    Show this thread
    Undo
  16. Jan 30

    You can't call survivor ship bias on things that really are just essential to learn and 'tried hardest' to teach. Thats simply falloff. But if the teacher was an asshole or the tools sucked, that creates it and can be fixed.

    Show this thread
    Undo
  17. Jan 30

    Of course many will still fail to make it to the 'end' 'and graduate, but atleast it won't be because of artificial barriers. Thats the best we can do.

    Show this thread
    Undo
  18. Jan 30

    As in your persistance/luck/upbringing that got you over that barrier is your bias. All that fell before it, its victims. So arguing for that way of 'teaching' is a form of bias. I think now we need to teach in something without barriers.

    Show this thread
    Undo
  19. Jan 30

    Someone explained survivorship bias to me once in: i made it from basic to C++. That was a huge barrier. Any barrier put up to move from 'newb' to 'pro' programming languages creates survivorship bias. So it'd be good to try to remove those barriers, as programming-IDE-builders.

    Show this thread
    Undo
  20. Retweeted
    Jan 30

    Too many see JavaScript as the common denominator for making cross-platform apps. Be it web, mobile, desktop or backend. Wasm is now supported by every major browser and there's no need to make JS your incidental language of choice. Free yourself!

    Undo

Loading seems to be taking a while.

Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.

    You may also like

    ·