unscaled

49 ms·

331.
by unscaled 5y ago
You've did notice the file you've linked to only has 7 non-comment/documentation lines, right? Now, to be fair, there are 50 or so lines of code in other files, but I would still love to see a useful Go package which is that
332.
by unscaled 5y ago
Almost 10 years have passed since this article was posted, and things are quite different now. Most of the popular web pages have cleaned up, and new startups are mostly following modern international design trends. Even sites that remained
333.
by unscaled 5y ago
The Ethiopian Airlines crew that crashed also turned off the stab trim[1]. The problem is that you couldn't turn off MCAS separately from the fly-by-wire trim control, so you could either have fly-by-wire with MCAS or manual trim contr
334.
by unscaled 5y ago
Most PAKE implementations actually make a security trade-off here - they protect the password transmitted over the wire, but you end up with a weaker password hash stored in the server's database. Modern PAKE implementations, like SRP,
335.
by unscaled 5y ago
Thank you for your kind words! > Regarding my point about migration compatibility - I would not assume that the only time anyone has moved from log4j to slf4j was when slf4j first came out. Slf4j+log back is also a drop in replacement fo
336.
by unscaled 5y ago
> but I have never seen anybody complain that "I switched to logback and slf4j and my jndi substitutions stopped working." SLF4J was created to replace Apache Commons Logging and Logback was created to replace Log4j 1.x . Both
337.
by unscaled 5y ago
It does have the RCE impact. You can still use gadget chains.
338.
by unscaled 5y ago
Both the licensing issues and the upgrade cost are largely myths. Licensing is only an issue if you want to keep using the free Oracle JDK, but there is seriously no need to. JDK upgrades were never drag and drop. When we upgraded Java 6 to
339.
by unscaled 5y ago
I migrated personally (or overseen migration) of many projects from Java 8 (and even Java 6) to Java 11. Modules in Java 9 were a bit controversial back then, so I guess that's the reason we hear a lot about it, but I haven't enco
340.
by unscaled 5y ago
I would go the other way around - it's entirely Oracle's fault for trying to be too compatible with unfortunate mistakes made in the past. Java Serialization is the root of all these things, and should have been deprecated and mor
341.
by unscaled 5y ago
The log4j maintainers seem to have realized that this (the "%m" in a PatternLayout doing lookups) is a bad idea around version 2.10 (released in 2017) or even version 2.7[2] (released in 2016). These versions both included changes
342.
by unscaled 5y ago
Until you get inside a city traffic jam, and then it becomes an acoustic indicator of something you already know: every square centimeter around you is covered by a car or a motorbike. I'm a skeptical horns help with anything in modern
343.
by unscaled 5y ago
In Israel the most common meaning is "Get off my lane, RIGHT NOW!", so I wouldn't be surprised if it's not just Syria but a big chunk of the Middle East that follows that rule. It could also be used to call another drive
344.
by unscaled 5y ago
Backdoored or not, the P-curves (or more specifically the standard algorithm we use for them) are hard to use and easy to misuse. djb dedicated an entire page listing all the theoretical issues with the P-curves and other elliptic curves[1
345.
by unscaled 5y ago
Not to mention Turbo Pascal was compiling faster than Go, on a single-core, in-order 20Mhz PC...
346.
by unscaled 5y ago
Moving from Java 8 to Java 11 or even Java 17 is surprisingly simple. Most of the work is just upgrading libraries which use internal JDK features or rely on brittle reflection/bytecode hacks. Java is a specifically strange beast here.
347.
by unscaled 5y ago
Yeah, I miss the good and simple times when Java didn't have all this unnecessary bloat like generics and annotations. We generously peppered our code with casts from Object and explicit boxing and unboxing, and it was good. Our code
348.
by unscaled 5y ago
That's not entirely a moot point. Java-the-language is mostly replaced by Kotlin and Java-the-runtime is wholly replaced by ART, there is also the Java standard library. New standard library features, or third-party libraries from the
349.
by unscaled 5y ago
> Thank god for that, because those feature are either horrible on their own or superseded by better ones. Are they though? I agree mutable data classes and property _setters_ are bad, but what about the rest? I personally like the idea
350.
by unscaled 5y ago
GAFAM is the one usually used for Big Tech, replacing Netflix with Microsoft. Netflix is not nearly as big as the rest of the group in terms of market cap, but the FAANG term was coined in 2013, in the Ballmer days, when Microsoft was far l
351.
by unscaled 5y ago
I was hesitating whether to mention unsafe code blocks or FFI, but the no language that gets thing done can avoid abuse of its escape hatches. Even Haskell has to deal with nulls when doing FFI.
352.
by unscaled 5y ago
The section that you're linking to in Effective Go does not state anywhere that "branches are clunky, they are so intentionally to make the points where your code branches much more obvious". It only promotes the concept that
353.
by unscaled 5y ago
This situation is unfortunately quite hard to avoid in the languages above since they either added null safety (or indeed any kind of type-checking) at a later stage (C# and Python) or they need to maintain compatibility with a language or
354.
by unscaled 5y ago
The "Go authors" (by that I assume you mean the Go team) have very explicitly stated that they view the current way Go does error handling as a major problem[1][2]. [1] https://go.googlesource.com/proposal/+
355.
by unscaled 5y ago
There have been many[1] proposals for streamlining error handling in Go, including some coming from the Go Team, like the check/handle proposal from Marcel van Lohuizen[2] and the try proposal from Robert Griesemer[3]. If anything, the
356.
by unscaled 5y ago
I think you meant the code: if err != nil { return fmt.Errorf("What I was trying to do: %w") } That's the correct and standard way to do error wrapping in Go since Go 1.13[1]. There is also Dave Cheney's p
357.
by unscaled 5y ago
It's not that simple. Let's say you memorized the main meanings of all characters in a Simplified Chinese character dictionary - each sentence you read will feel as if you've understand the verbs and very basic nouns in the s
358.
by unscaled 5y ago
This sounds like elitism in disguise to me. Sure, there are some cases when you want quick and dirty and just glue some system together, but most production code out there has some more important business requirement than "understandab
359.
by unscaled 5y ago
I think you're talking about this blog post: https://web.archive.org/web/20110410011410/https://gojko.net... I took a peek at the code and it looks like nothing has improved since then. For instance
360.
by unscaled 5y ago
It's not like the only two choices you have in the world are UUIDs and auto-incrementing sequential IDs. There are many better alternatives to UUID for the general case in which UUIDv4 is used, that provide some of the following advant

More ›