matthew_kuiash

Wow! I thought it was just me. I find it incredibly difficult to read icons. Even small design changes throw me - the most annoying was the change in speaker icon across versions of Windows. The bigger the icon the less of a problem it is but those fiddly toolbar icons throw me all the time. I have mentioned this to a few folk but honestly thought I was on my own.

Totally this ^^^. I still battle with CSS. I have no love for it but the best way I've found to approach it is to have some idea of what I want to achieve visually and work from there. Almost everything one would seek to achieve has been done by $someone and is out there on the internet. Steal it! Sometimes it's blog posts, sometimes I just scrape other sites (modern browser really help here). But yup, grid, box, floats. MDN rocks.

Yup. Once I saw the 24" iMac I knew the 27" had had it's chips. 30" won't actually be much bigger than the 27" if the bezels shrink to almost nothing - which seems to be the trend.

I can't wait. Sadly I agree with you. This level of control is irresistible.

Why do they have that right? Here's a car analogy - If I buy a Ford pick what right do they have to stop me doing donuts in it? Or maybe fitting a swimming pool in the back. Maybe I want to drive it around my ranch on fire. If an individual wants to use this software on their Facebook feed I really can't see what legal right FB have to prevent them. OTOH - something was probably "signed" in a EULA to prevent this.

Needs templates. That'll fix it.

I needed a good giggle and there it is! Thanks! I enjoyed that!

1 sample latency or it didn't happen.

The speed of sound in air is ~330m/s so sitting about a metre away will produce ~3ms delay. However the speed of the vibration through human flesh (far denser than air) is about 4 to 5 times faster than the speed in air. You will "hear/feel" the sound transmitted through your body far faster than the sound transmitted through air. This maybe why I'm always seeing this magical "1ms" value.

Love this book. Easy to grasp. Fun to code and ever so pretty.

Logo was one of the 3 I first picked up on Assembler, BASIC and Logo. My first computers weren't capable of running LOGO (no real display). I didn't have a LOGO interpreter so I coded one in BASIC. By god it was slow. But I did pick up structured programming and it led me on to LISP (and SASL/CLU,Pascal,Modula 2). Somehow I still ended up using C/C++ daily. I guess that's just how it goes. But LOGO was and is nice. It (almost) has what my dad calls IKR (Immediate Knowledge of Results) and if LOGO were to develop further it is exactly the area of realtime interactivity I think it should move. Great language with a lot of thought put into it but still very much a product of its era.

Uummm. Is this accelerated due to the inherent fuzziness of neural style calc or because they have to models working on NN/TF/GPU style hardware? I skimmed and couldn't find an answer. As for the "is it accurate?" question. No, no it isn't but then neither is any other model - it just has to be good enough over the time frames concerned. This is more like weather forecasting than chess.

TBF 1/2 of them weren't even born...