Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
unscaled
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
75 ms
·
571.
▲
by
unscaled
10y ago
I did wrap JWT/JWE with a library lest somebody else in my company would get the bad idea to implement directly, and yes, the first thing I've done was to limit the signing algorithm to a single specified algorithm (HS256 for ever
572.
▲
by
unscaled
10y ago
The alternative is pushing plain public keys over an authenticated channel. You usually don't need the complexity of X.509. That being said, the aforementioned authenticated channel will more often than not be TLS, which does happen to
573.
▲
by
unscaled
10y ago
Agreed. Revoking all user sessions instead of a specific token is the common case. The only usage I see for revoking a specific token is when the user is deactivating a specific client.
574.
▲
by
unscaled
10y ago
Most of the advice holds true, but there's one bit you should happily ignore: don't uglify your code with external include guards - that is put your include guards in the included file. Modern compilers perform include guard optim
575.
▲
by
unscaled
10y ago
All true. But OP was never trying to argue that PHP is more complex than other language, but instead claimed that once you get to the point of requiring complexity, PHP doesn't get to have the "it's braindead simple" adv
576.
▲
by
unscaled
10y ago
The combination definitely seems overwhelming, but each tool is a solution to a real problem. That's where the "(real)" in the title is coming from. Yes, if you're only writing a hello world app you certainly don'
577.
▲
by
unscaled
10y ago
Exactly. I've seen many monoliths which were bloated with pieces of functionality developed for specific needs that other parts of the company had. So your shopping cart API would get promocodes, and coupons, and express delivery, dona
578.
▲
by
unscaled
10y ago
I beg to differ. Microservices are certainly overhyped, but they aren't as bad as the ORBs of yore. I see 3 key aspects which are entirely different: 1. Microservices do not necessarily encapsulate storage at object level. You could ce
579.
▲
by
unscaled
10y ago
While I don't think refactoring single use function is a win in every case, I think it makes sense when what you're trying to do in the block of code could be conceptually separated from the rest of the function - and named approp
580.
▲
by
unscaled
10y ago
You're not crazy. I also have vague memories of maps being more obnoxious in Go. :) The facts are that map literals did change a bit in Go 1.5 (i.e. fairly recently), full literal specification for values could already be elided back t
581.
▲
by
unscaled
10y ago
Second that. I've seen these signs in many places in the Indian parts of the Himalayas. Even the BRO wikipedia page shows a sign with exactly the same witticism from Ladakh. So this makes this a purely Indian sense of humor.
582.
▲
by
unscaled
10y ago
All of the problems outlined are relevant whether you pre-fork into multiple processes or use different threads. I don't see what it has to do with pthreads.
583.
▲
by
unscaled
10y ago
WaitForMultipleObjects sucks, but that's because it got very little love since Windows 95. That's because Microsoft seems to have completely abandoned the Reactor (select/epoll wake-on-readiness) pattern in favor of the Proac
584.
▲
by
unscaled
10y ago
I get the problem, but I don't think experienced C++ developers should pamper inexperienced (or unwilling to learn) C++ developers by avoiding features that are considered best-practices. Template programming with Boost.MPL? Sure, I re
585.
▲
by
unscaled
10y ago
Definitely. Though I admit I prefer automation or red tape where possible. What you can say about Japan, is that since technology-wise it tends to be behind the US (of course this too is a gross generalization), you can expect most non-star
586.
▲
by
unscaled
10y ago
I'd second that any day, even though I'm probably guilty as any at generalizing.
587.
▲
by
unscaled
10y ago
Which is what we did, obviously and nobody is allowed to run anything manually while SSHing to production. But there was a tremendous organic resistance to that from the very same "culture of excellence in engineering". "How
588.
▲
by
unscaled
10y ago
One of thing that I learned the hard way about "Japanese companies" - despite western conceptions, every company in Japan has its own unique culture (and takes pride in having its own culture!). What's more, often departments
589.
▲
by
unscaled
10y ago
Yeah, the legally elected leader, according to the Constitution, is Donald Trump. That still doesn't mean the majority of Americans electing them. Parent was assigning the responsibility for his election to all American citizens, but i
590.
▲
by
unscaled
10y ago
The government of Saudi Arabia doesn't officially sponsor any terrorist group (what royal family members do unofficially with their "own" money could be quite different :(). But that's not even the question. The question
591.
▲
by
unscaled
10y ago
The US used to do many nasty things during the Cold War, in the name of blocking soviet influence, and the overthrow of the Mossadegh was just once. Then again, this was over 60 years ago. If we go by the same measure, Germany and Japan, bo
592.
▲
by
unscaled
10y ago
The 'original sin' of C++ is not having both references and pointers, but trying to remain compatible with C. That means that Stroustrup couldn't have ditched pointers, but if he wanted to implement operator overloading for v
593.
▲
by
unscaled
10y ago
1992 was just the year MFC came out. I would go as far as saying that C++ of the early '90s was at its Nadir of inelegance. I'd go as far as saying that C++ frameworks of the early 90s were the absolute nadir of elegance. STL only
594.
▲
by
unscaled
10y ago
Gogland's non-standard formatting is one of my pain points. But the standard go* tooling doesn't offer any proper refactoring. Unless if by refactoring you mean "Jus' renaming my functions and variables and nothing else,
595.
▲
by
unscaled
10y ago
I explicitly mentioned Gogland (the Jetbrains IDE). I'm not a fan of heavyweight editors (including emacs), and I'd gladly just use vim for Go if vim-go had refactoring support beyond the useless gorename. Gofmt works nicely acros
596.
▲
by
unscaled
10y ago
Some of it, probably. But some are probably using Go out of necessity (your company enforces Go), or because they still think Go is their best pragmatic option, lack of generics notwithstanding.
597.
▲
by
unscaled
10y ago
This mentions weak IDE support as one of Scala's pain points, but Go has very much the same problem, and the language is vastly less complex. The two best IDEs for Go right now IMO are VS Code and the EAP Gogland, but both of them are
598.
▲
by
unscaled
10y ago
For loops are yet another of these useless abstractions introduced by the academia, this time straight from the design-by-committee language ALGOL 60. We all know real programmers used gotos.
599.
▲
by
unscaled
10y ago
Developers have been using C and a bunch of other imperative languages for years. They obviously, created software two order magnitudes more complex than CockroachDB (or Docker, or Kubernetes, or etcd). We used to write entire operating sys
600.
▲
by
unscaled
10y ago
Lucky bunch indeed. I'm 9 months in and still missing map(), flatMap(), let alone more advanced FP. I guess this is a matter of personal preference, but I definitely consider: users.filter(_.active).map(_.email) to be easier to
More ›