woojoo666

60 ms·

691.
by woojoo666 5y ago
You might have already seen this but in case you havent, there's a famous talk about this called "the coming war on general computation" ( https://www.youtube.com/watch?v=HUEvRyemKSg ), and much of this has alr
692.
by woojoo666 5y ago
By "making data private" I meant encryption
693.
by woojoo666 5y ago
While I think itcs bad to use obfuscation to hide security holes, I do think obfuscation has it's uses. If there's reasons to make data private, then there's reasons to make execution private as well. Not to mention, it was r
694.
by woojoo666 5y ago
type inference is a beautiful thing and I hope Typescript adds it someday
695.
by woojoo666 5y ago
totally agree. That's why I think libraries and other mature code should use static typing, whereas I like to use dynamic typing for code that I am prototyping. This is why I love Typescript, you can have both :)
696.
by woojoo666 5y ago
I've found that "throwing things at the wall" can be very helpful sometimes. It isn't necessarily a linear path from designing a solution -> implementing it in code. Sometimes writing some preliminary code can help fl
697.
by woojoo666 5y ago
I prefer dynamic typing when writing code that I perceive as "volatile". This is especially true when it's a piece of code that's currently only being worked on by me. Static typing adds boilerplate that feels cumbersome
698.
by woojoo666 5y ago
> you've got grounds for pretending you didn't build your machine to do exactly that. I believe all laws about intent have to deal with determining who is pretending and who isn't. But these laws still exist, because there
699.
by woojoo666 5y ago
ah you're correct, I misunderstood the meaning of Working Note. It seems like Safari is adding support for WebM this year, but even so since it's still an editor's draft I think it's reasonable to expect websites to prov
700.
by woojoo666 5y ago
because [WebM is a web standard]( https://www.w3.org/TR/mse-byte-stream-format-webm/ ) so it's natural for developers to expect browsers to support it. If Apple didn't like it they could have pushed back b
701.
by woojoo666 5y ago
even if a proof is well established, porting it to a proof language allows other proofs to build upon it, like importing dependencies in traditional software development. And the bigger the library of proofs gets, the more possibilities the
702.
by woojoo666 5y ago
It seems like the bigger issue is that Apple isn't playing a bigger part in developing web standards. If Apple doesn't like certain features, they should fight to keep them from being standardized, instead of just refusing to impl
703.
by woojoo666 5y ago
To be fair many, many people can also get everything done on their phone too. An ipad gives more screen space and better multitasking. A 2-in-1 (like a Surface Pro) gives even better multitasking and file management. It's all up to wha
704.
by woojoo666 5y ago
afaik a lot of extensions aren't fully supported yet. I tried about a dozen different tab managers on FF Nightly, none of them worked. I'm guessing the Tab API or something isn't fully ported yet
705.
by woojoo666 5y ago
Most companies ask you to install work profiles and such only after your sign on. It would be exceedingly petty of them to fire you for something like that, especially at a tech company that will definitely have the money to provide ~$300 w
706.
by woojoo666 5y ago
it's not that complex. If you drag it to the notepad icon, it opens a new process. If you drag it over the icon and then over to one of the small window previews that pop up, it sends the file to that window