PostThisTooFast

What's alarming is the continued existence (and respect) of software patents.

Until software patents are abolished, developers and consumers will continue to be ripped off.

Calling Adobe's mess a "spec" really gives it too much credit.

Now they've reduced themselves to "breaking" compatibility every couple of months to try to get people to maintain their software lease.

Despicable trash.

Apple often refuses to learn, or in fact "forgets" what the industry already knew.

Another example: Forcing people to use an E-mail address as their user ID. This is a security and practicality disaster. Not only do people now have multiple Apple IDs (which Apple huffily refuses to consolidate) that split their iCloud and App Store purchases into a mess, but a large proportion of the public undoubtedly thinks that they have to use the same password for this ID as they do for their E-mail account itself.

Everyone's E-mail address is on spammers' lists. When you combine that with a list of the top passwords, you get thousands if not millions of compromised accounts.

STUPID.

Yeah, they should've gone with full-sized HDMI ports, since they have the room.

Yep, the ability to construct a mental model is the most critical. If you can then keep it organized when you translate it to code, I'd say you're well-suited to the work.

I wonder how many people have this ability, especially when reading about organizations like the one that went to Appalachia to teach people in depressed areas to program.

Doesn't Backblaze delete copies of volumes that you haven't accessed in a certain amount of time?

Then those devices are to blame. Disabling the volume control is common for all digital outputs, not just HDMI. There's an absolute scale for volume in the digital domain, so there should be no vast disparity from different devices unless they're doing something dumb.

Analog sources could vary in volume because they provided voltage across an analog input. When CD players came out, they had notoriously "hot" outputs, meaning physically higher voltage. Not so with digital connections.

Not to mention that the biggest problem, at least in music, isn't the absolute peak (or normalization), but rather dynamic compression.

Everything mastered (or "remastered") since the late '90s has been destroyed with dynamic compression to make it "louder." It's the biggest crime against art in our times, but is poorly understood even by musicians who complain about it. Interestingly it's the older ones, like Neil Young and Bob Dylan who have been the most vocal about it, but incorrectly attribute it to data compression or sampling rates.

Yes. Catalyst is a kinda-clever but janky solution. It basically puts the iPad simulator on the screen.

The '90s were full of ballyhoo about object orientation and "soon we'll be bolting together software with off-the-shelf components."

Thanks to the failure to standardize C++ ABIs (among other reasons) that didn't happen... except for VBXs. You really could throw together a CRUD app pretty quickly with off-the-shelf VBX controls.

Definitely. The automated system can’t ID covers.

"Your complaint is like saying that having to copy and paste with ctrl c and ctrl v is non discoverable in Windows with a two button mouse because in Linux it’s just select text and middle click somewhere else."

No it isn't, because those functions have equivalent menu items.

Easter-egg controls in a GUI are a different (and inexcusable) story.

Kinda tired of the proliferation of languages coming out of Google, whether they actually created them or not.

If Go is so great, why was Kotlin released four years later and made the standard on Android? It's annoying enough to have to use Swift and Kotlin for iOS/Mac vs. Android. Now Go? What happened to Dart?

Then there's Rust. What about next week?

Remember when Apple was going to adopt ZFS as Mac OS's file system?

Then... nothing further was heard about it.

Really? This deserves a post of its own!

Actually, that's how other countries are dealing with the U.S.

I don't see it as a sign of "doom," but rather more regression. It took YEARS for Apple to admit that their keyboards were shit, and they still haven't admitted that the emoji bar on their so-called "pro" computers is an embarrassing and failed gimmick. In fact, they've doubled down on it and now don't offer ANY proper laptop keyboard.

But that's off-topic to some extent; I scanned through this page looking for some good news for developers. Topping my list is support for SVG assets. NOPE. WTF? Android has had this how long? Apple's "@2x", "@3X" bitmaps were amateur-hour to begin with, but a decade later? No vector support?

Come on.

And still no user-definable color schemes. Windows (and Unix GUIs, for that matter) had them for decades, while Apple forced its late-'80s inverse scheme on every user that whole time. The hard-coded "dark" theme is a half-baked, belated admission that staring into a glaring light bulb with black text on its surface all day may not be the best way to work.

This would also have been a great time to abandon the single menu bar, but nope; that poor decision continues to plague Mac users. Really, this should have been canned in the transition to OS X, but now there's even less of an excuse.

I'm sure there will be some good changes, but from this list I'm not encouraged. Getting rid of the distinction between toolbar and app content... WHY? The "flat UI" experiment was a failure. Let's continue to take tasteful steps back toward GUIs that communicate in universal visual terms whenever possible.

Don't know if this is related, but after initially being excited to hear about GraphQL, I was very disappointed to find that it doesn't seem to offer any way to (in effect) express joins.

Am I missing something here? Has this been addressed?

Thanks.

NAILED IT.

Touchscreen UIs are not for creating. They're for taking what you're given, pecking at giant canned buttons in a dumbed-down UI.

A pigeon can peck the colored button to get a food pellet. That's tablet UI.

Seemed fine until the end, where metaphors have been mistaken for new words. Example: "dumpster fire."

Webster's continues its descent into stupidity.

Also: Don't capitalize every word of control labels. That's amateur-hour. They're not titles or proper nouns, and capitalizing them leaves you no option when you DO refer to a title or proper noun.

He reminds me of an entire team of programmers who turned up their noses at VB, insisting that they work in VC instead. When, predictably, the VB prototype of the product worked perfectly well (the whole app was database-driven)... they were all fired and the product was finished by one designer and a team of contractors instead.

In the '90s, we were all supposed to look forward to a "marketplace of pre-built objects," which could be bolted together to build applications. That didn't materialize, because (as I understood it) of the industry's failure to standardize compiler output so that object libraries written in C++ could be binarily compatible with other software (someone can elaborate on this if they have more details).

But there was one exception: VBXs. We did indeed write a lot of software for some very high-profile clients using drag-&-drop VBX controls, especially things like data grids. VBXs did largely deliver on the promises we all heard at the time.

The other big hype at the time was how the newly unified UNIX camps were going to wrest the desktop from Microsoft. We all know how that turned out (except the people who are still saying the same about Linux...)

OK, this seems pretty cool.

I hope Microsoft has fixed a few of these things though: http://goldmanosi.blogspot.com/2012/05/visual-studio-is-it-g...

The graph's axes aren't labeled. Therefore it isn't informative.

You don't "grow" revenue. You don't exist a new service. You don't die germs.

You use transitive verbs when you want to direct them at an object.

Doesn't this prevent Nevada and anyone else from demanding source code for slot machines and other gambling machines, to audit it for backdoors and other flaws? The last I heard, they're not even allowed to use off-the-shelf video drivers. Every line of code has to be (theoretically, anyway) audited by gaming authorities.

I suppose those are usually delivered under a "negotiated contract."

"The idea is to introduce real-world entity to UI/UX"

No, that should be REINTRODUCE. The whole point of a GUI is that it's intuitive. The depicted controls should bear essential visual qualities of real-world objects, like buttons. Does the button look like it's sticking out from the background? Then it's not depressed. And so forth.

"Flat" UI is an idiotic regression that has set GUIs back decades. Come to think of it... did they ever suck as much as "flat" UI? Now we have entire interfaces that are an Easter-egg hunt. It's pathetic.

Interesting that it's a sterol, considering that corticosteroids CAUSE cataracts. Not to mention destroying retinas by inducing central serous retinopathy. We're talking allergy nasal sprays like Nasonex, eye drops like Tobradex, and shots like Prednisone.

Don't use corticosteroids unless it's a dire situation (pretty much never).