unscaled

60 ms·

481.
by unscaled 8y ago
Or Construct: https://construct.readthedocs.io/en/latest/
482.
by unscaled 8y ago
I guess this was your point, but the problem is how Java does does type erasure. With Haskell type erasure is an implementation detail, but with Java it leaks into the compile-time type checker. For instance, you can't have both these
483.
by unscaled 9y ago
> To achieve the same result with recursion requires a whole other can of worms: memoization and tail recursive style and compiler optimizations to shed stack frames. It’s a lot more work to understand all that (to get to an equivalent s
484.
by unscaled 9y ago
Well, it's already been done for LORD: http://lotgd.net/ I can see other ways you could do that generically for every door game: 1. Run the game in local mode inside a DOSBox running under WASM in a webpage. 2. Run a c
485.
by unscaled 9y ago
Yes, theoretically speaking this distinction might have been useful, but so would have been combining hieroglyphs and hangul jamo and the ability to define an entirely new CJK character by specifying components and placements would have bee
486.
by unscaled 9y ago
Well, there is really no way to solve this other than using a language-specific font or markup to indicate the language of the text. The first solution is probably the more common one, since there are very few international fonts that act
487.
by unscaled 9y ago
I think I've yet to met a Japanese person who was even mildly unhappy to see their name rendered incorrectly due to Han Unification. It seems like when Unicode came out, the TRON guys and some other Japanese engineer were pretty vocal
488.
by unscaled 9y ago
He didn't have any bone to pick with the language _per se_, but rather with the inability to easily replace an app running in the browser with a modified version, even though the license allows you to do so. It was arguably a lot easie
489.
by unscaled 9y ago
This should be pretty common knowledge to any linguist who studied historical linguistics, although if you never did any historical linguistics you could easy miss that. This should also be common knowledge to anyone who studied late-mediev
490.
by unscaled 9y ago
To extend on that, I can give list the lessons I learned from actually running a similar scheme internally in production for a while now: 1. Give developers the minimum amount of knobs. If they need to choose between 'auth', &#x27
491.
by unscaled 9y ago
I would happily do away with v1 completely. In my unfortunate experience you're still giving developers enough rope to hang themselves with by choosing older ciphers just because they are well-known.
492.
by unscaled 9y ago
They are not irrevocable - just harder to revoke. If you want something that avoids storing all tokens , you can use a blacklist. You don't even have to check for revocation on any call - you could perfectly use short-lived (say 10 mi
493.
by unscaled 9y ago
Considering Chrome's market share, it's enough for Chrome to break something to force server-side action. Distrusting Symantec certificates is a prime example, I think. The breakage rate for distrusting all Symantec certificates i
494.
by unscaled 9y ago
You can start with running your JSON data (or whatever serialization format that you choose) through NaCl/libsodium's crypto_secretbox() and you already get more than what JWT offers by default. It still doesn't include every
495.
by unscaled 9y ago
I find it hard to recommend JWT unless you're already a security expert. This is unfortunate, since JWT was meant to bring client-side tokens to the masses, but the reality is that: 1. JWT has amazing cross-language support, but most o
496.
by unscaled 9y ago
It seems like a wild exaggeration to me. Japanese definitely has it's share of imagery and wordplay. It's just that most video game scripts - especially from that era - tend to employ a language that is straightforward and functi
497.
by unscaled 9y ago
I think the illusion of competition mostly comes from how Go was touted when it first came out. To quote the google announcement: "For that reason, Some smart Google engineers decided that it’s time to address the limitations of C and
498.
by unscaled 9y ago
Without using containers or fragile (and not very portable) executable wrappers you need to manage the JRE, JAR files and the right classpath. With go you can just run 'go build' and get static executables for all common platforms
499.
by unscaled 9y ago
Then what are the design patterns for Scala?
500.
by unscaled 9y ago
It's a matter of platform and the libraries that you're using. After all, back in the days we had 360k floppy disks, and executable written in C which did much more than just printing out "Hello world" would fit comforta
501.
by unscaled 9y ago
Well, if you're doing microservices you're usually nullifying most of the benefits of this kind of architecture if you're just deploying them on war files on a single application container.
502.
by unscaled 9y ago
"Around 12,000 BC, the world’s population stood at between two and four million; by 2000 BC, it was around 25 million. But the vast majority of people had no contact with states as late as the end of the 15th century – Europe’s middle
503.
by unscaled 9y ago
I think this is yet another misconception that might come out of theoretical political science (or the ignorant press). The political difference between the Early Middle Ages (a.k.a the dark ages) and the Roman empire wasn't the lack o
504.
by unscaled 9y ago
The average life expectancy in Thomas Hobbes' days was even less, generally estimated between 35-40. When historians claim that hunter-gatherers generally had a better life than farmers, they don't have modern urban middle classes
505.
by unscaled 9y ago
Which shows you the limit of verification toolsets vs. a verifying compiler. To verify that the code is 100% free of uninitialized reads or uses-after-free the static analyzer would have to scan through all possible permutations. Sure, you
506.
by unscaled 9y ago
It wasn't really. Otto was touted as a long-term successor to Vagrant, it never gained much traction and ended up being decommissioned a year later: https://www.hashicorp.com/blog/decommissioning-otto/ Vagran
507.
by unscaled 9y ago
If you are not the size of Facebook, suing Facebook for a patent violation will be prohibitive to you, period. http://www.businessinsider.com/just-so-were-clear-facebook-t...
508.
by unscaled 9y ago
Well, it could be worse: 1) Stuff that keeps you insecure (a.k.a ISO 27001 ISMS stuff) 2) Stuff that somewhat helps, but is covered by fluff (a.k.a. PCI-DSS) 3) Stuff that actually keeps you secure. PCI-DSS at least gives you a sledgehammer
509.
by unscaled 9y ago
Mastering a language is not the same as reading the entire spec, or even internalizing that spec. Scheme or Forth or Io are all probably smaller than Go. Perhaps even smalltalk is (the Smalltalk 80 spec is larger, but contains some of the l
510.
by unscaled 9y ago
My subjective impression (supported by informal surveys [1]) is that most Gophers come from a Python or Node.js background, doing mostly network code, DevOps automation or CLI tooling. Rubyists are less likely to fall in love with Go, given

More ›