Slackwise

Just delete/block the NYT cookies.

> I'm a PM for Confluence Cloud and we're always trying to make it better.

Can you guys please make Ctrl-S save and not exit editing? My muscle memory is costing me 10+ seconds of load times every time I type a paragraph and reflexively save, getting dumped back to the view mode of a document. The slow load times exacerbate the problem tremendously. I honestly don't know a single product that treats Ctrl/Cmd-S as "Save and Exit" so this is just a baffling UI/UX design decision.

I don't know a single database that is identical to another in implementation and just has a different UI/UX for it. Every single database has something specific for it in terms of implementation.

(Unless I guess we're talking forks of MySQL.)

I don't know if maybe you have a good example...?

What comes next, IMO, is semantic version control.

Version control that is aware of changes not at the file and line level, but at the function level, the module level, the library level, the language-specific construct level.

(Rich Hickey, creator of Clojure, played around with this idea, but I'm not sure where it went.)

That's more a case of UI rather than implementation, yeah?

What's stopping us from just using those words to describe operations with Git?

I mean, what Git is, is a data structure with a set of operations on it, and the design of that is pretty fundamental at this point. We'd need to see something more novel[1].

(Sidenote: Git almost seemed an obvious trajectory for version control given how problematic file-based approaches have been. I've used far too many version control systems, including "ancient" awful ones like Harvest[2], and it just felt inevitable that we'd one day rely on an "always-branching" model.)

[1]: I did think of something more novel: semantic version control (https://news.ycombinator.com/item?id=25537455)

[2]: https://en.wikipedia.org/wiki/CA_Harvest_Software_Change_Man...

Nintendo seems to do customer support fine with hardware, but their treatment of digital products and data is extremely hostile.

The Switch has a backup feature, but the backups are hardware ID locked, so if you lose your Switch and get a replacement, lol, the backups are useless. This is made worse because even though you may have a physical cartridge game, the actual save files are on the machine.

Personally I had a run in with this when I upgraded to a 3DS XL, and I didn't check for dead pixels until after I transferred all my data. They locked the transfer feature for a week+ so I couldn't go and get my device replaced for a week, and my data was held hostage on a machine with stuck/dead pixels dead center on what is already a low resolution display.

> I personally have found FP hard to debug.

I can very honestly say pure functions are the easiest thing to debug and test: Inputs, outputs. Trivial for unit testing.

I can't speak for MLs/Haskell, but debugging pure functions in any language tend to just be glancing at the stack trace, seeing the values on the stack going in, and then seeing where the unexpected wrong output came out, and being fairly confident knowing the issue is going to be in that function.

> The "naked state" of imperative programming

Are we including OO in this definition? The fundamental design pattern of OO is to encapsulate state. It's anything but naked, always being wrapped in object instances, only accessible via getters/setters, scattered into a million pieces across many instances of the system.

Conversely, Clojure has the most naked state ever. There's usually little to no state, and the current state is right there on the stack. Most simple Clojure programs with state have a singular atom aptly named "state" which is passed around, easy to inspect and modify as it's a simple data structure.

I think, ultimately, there's a common conflation of "Functional Programming" meaning "Declarative Type-Driven Functional Programming", when the reality is there are alternatives to ML/Haskell, aside from applying Functional patterns in "non-functional" languages.

Math is perfection. So, it depends on if you consider math to "exist" in this world.

> Auto-generated, type safe entities from source to client, including relationships = fewer bugs

Are you saying that your client (interface) has a direct relationship to your database schema...?

Eh, I've been using https://quire.io for Flowy-like task management for my team and it's been great.

Relevant here as it has single-key shortcuts for actions and is an infinitely nested task list, but unlike Flowy, works way better for teams, with GitHub integration, etc.

I'm more interested in the Nix/Guix approach, where you get the benefit of exact version linking, but also an "immutable" version controlled OS, so things like Puppet aren't necessary to manage state. (And likewise, deploy small VMs/containers with just the package manager tools without needing Docker as the entire OS state can be rebuilt using a definition file/version hash.)

Actually, if you have a Wikipedia account, you can save custom CSS (and even JS?!) to your account:

https://en.wikipedia.org/wiki/Special:Preferences#mw-prefsec...

Pretty sure it will not. Nothing is lazy in JS by default:

> One caveat of spreading iterables: JavaScript creates an array out of the elements of the iterable. That might be very wasteful for extremely large collections. For example, if we spread a large collection just to find an element in the collection, it might have been wiser to iterate over the element using its iterator directly.

> And if we have an infinite collection, spreading is going to fail outright.

http://raganwald.com/2015/02/17/lazy-iteratables-in-javascri...

> In a new research paper, Thompson and colleagues argue that it is, or will soon be, impossible to increase computing power at the same rate in order to continue these advances. This could jeopardize further progress in areas including computer vision, translation, and language understanding.

It was always inevitable for a new "AI" technique/algorithm to plateau. You'll eventually run into a wall with AI approximates. Until we reach General AI, this will continue.

As much as I love vi, this makes sense.

If only this could last.

Working out is bike rides for me, so that means taking my hand off the bars. I mean, in comparison to a phone, what does the watch offer when you're lifting? How will you dismiss a notification? What's the real difference between just picking up the phone or having the phone or a tablet mounted somewhere you can see at all times?

I do a lot of walking downtown and half the time I have a cup of coffee in my hands or something else. Responding or interacting with the watch becomes impossible without two hands or I guess talking into it.

You need two hands to use a watch: one to bring it your face, and the other to interact with it.

Believe me, I want to use a smart watch; it feels like every kid would have wanted one back in the day. But when you think about them, they're not as useful as they seem due to many factors, and I think most people get that, because you don't see many people wearing them. They're definitely still a niche product.

But how many people wear glasses? What if they did more than help you just see better? How many people might drop contacts for that value, even? (Some people wear glasses over contacts purely for fashion.)

You don't have to do anything to see information in your always-present glasses, and you only need one hand to operate them. Alternatively, a mic would be closer to your mouth so that's more functional than bringing your hand to your face to give commands as well.

Smart Glasses?! Please!

I've been waiting since forever. This is the only "smart" tech I've been so interested in. I already wear glasses, why not make them more useful?

Meanwhile watches get in the way of using keyboards and interacting with things, and you constantly take them off. Can't use them if your hand is busy either, like holding a drink. They're not as convenient as they seem.

Years ago, I needed to parse and view custom logs from our proprietary app, and I needed to do it now, so I cranked out a little Ruby script. But then I needed to share it with a non-programmer... so moments later, I slapped on a little Shoes GUI and it was good to go.

I believe the same tool is in use even now, over 10 years later.

Probably the fastest script-to-GUI iteration I've ever done, and a good showcase of Shoes' simplicity. (Although, the GTK gem is actually pretty easy to use as well, and my most recent conversions have been with GTK.)

> pour millions into a world class engine for devs

That developers pay millions to license and use. This isn't charity work.

> build out the first "full house" competitor to Steam

So they can control the market as a replacement for Steam, a superior platform that has (a) an instant return policy [1], (b) the ability to emulate input for any game for the disabled[2], and (c) the ability to share your entire game library with family without having to share accounts and save files.

[1]: Obviously hasn't always been the case. [2]: Via Big Picture Mode, which allows you to use any controller for any game and remap inputs for games that have no such settings. A total blessing for anyone disabled or with a preference for different controls.

That's pretty clever! A good writing surface other than a wood table can also improve the comfort of writing as well.

As a lefty, the ink's drying speed is key, but also, the size and shape of the nib. Lefties should be using big bulbous bold 1.0+ tip nibs that glide across the page instead of stab into it.

Unlike a rolling ball pen, it won't skip or fail to roll with pressure due to the rightward angle-of-attack against the paper, so a proper fountain pen is actually better than most other pens for us lefties. First time experiencing smooth writing in my life.

Ultimately, the enemy of lefties is the pointy tip, and the rolling ball that's expected to be rolled against the paper, not pushed against it. Felt-tip pens work just fine for us, so those pen Sharpies are alright, but so are the 1.0 bold tip roller ball pens from Pilot, at least all the Pilots I've tried. Can't say all the others work as well.

Uhhhhhhhhhhhhhhh, alrighty then........ can't edit or even delete now. Thanks for the heads-up....

(Mods, could you change it if you see this?!)

This is known as Zawinski's Law[1]:

https://www.jwz.org/hacks/#:~:text=Law%20of%20Software%20Env...

[1]: Zawinski as in "jwz", Jamie Zawinksi: https://www.jwz.org/about.html

There are a lot of young developers that just have no context for what Microsoft did in the past. If you bring up their past, they say "that was so long ago" or "but they've changed!"

But public companies are not people.

Of course they change -- tactics -- and try to gain control again. Everything they do will in the end have to be justified to their shareholders and how it will either gain them profit either now or in the long run, and as soon as the fickle-minded shareholders change their tune, out goes Nadella, and we'll get another Balmer or worse.

Actually, I read a rumor somewhere that was planned for Windows 10 as part of UWP, which already supports JS apps.

They've already gone fairly far in integrating PWAs with the new Edgeium, so we'll see where this goes. (Your installed PWAs appear in the control panel for uninstallation, for example, which even Chrome doesn't do yet.)

Markdown is plain text.

The output of Markdown processing is not.

Markdown is intended to be readable without processing as its syntax is mostly based on plain text email conventions. You should consider the ability to process Markdown to another output format to be an almost incidental benefit to using Markdown, rather than its primary function; meaning, Markdown syntax conveys semantics even without processing.

Its line behavior is based on plain text email client conventions, and plain text editor behavior, which many do not by default perform line wrapping, nor necessarily should, depending on user preference. Meaning, a Markdown file should be readable with line wrapping turned off, hence why it consumes line breaks, unless you use two spaces at the end of a line to override this behavior. (Think of the two spaces as an invisible rendering hint to Markdown processors.)

Email line length specifications: https://tools.ietf.org/html/rfc2822#section-2.1.1

Skype for Business is obsolete, though:

https://www.theverge.com/2017/9/25/16360072/microsoft-teams-...

Haven't used Xfce in a few years... is there finally a native Dock/SuperBar or a proper plugin that isn't some hack that nests alternative docks inside a panel?

I actually like the domes as they are. What I want is, somehow, to increase the spring tension after the dome collapses, so that I don't slam into the baseplate.