jawngee

browsersync syncs up everything, so I'm sort of failing to see the difference between this and a few tiled windows side by side (what I currently do) with browsersync sync'ing scrolling and clicking. You're likely already using it as part of your webpack dev flow anyways.

I have Viettel fiber and I very rarely feel the effects of cable disruptions. Most times I wouldn't even notice until someone complains about it on an expat or neighborhood group.

This is less the case for people using other providers.

I wrote two MIDI sequencers in Delphi and a couple of audio editors.

A lot of audio software and VST plugins, in the early days, was done in Delphi.

https://web.archive.org/web/20130121065235/http://www.sonics...

Really, QC was one of the cooler things Apple has done since HyperCard.

I wrote a video editor that allowed you to use it to build plugins with it: https://vimeo.com/121663242

Unfortunately, life got in the way of finishing it.

> reusing connections to databases

pgBouncer and ProxySQL are going to give you a better bang for the buck than a stateful web app will.

What new program?

It's a game I describe as "addictively boring". I'm about 300+ hours in. It's my version of a rock garden.

Yes but a lot of users with real world experience.

"Getting your VR legs" is definitely a real thing.

Can you really steal CSS though?

I'm doing pretty well selling a WordPress plugin, https://mediacloud.press/

It's an equal mix of rewarding and frustrating. It's a lot more work than you'd expect and now I've a deep understanding of why support tools are as obtuse as they are.

It's generating enough income that's livable and freeing me up to focus on other related projects. I'm going to be launching a SAAS version of the plugin later this year.

This article is mostly nonsense.

I've found there are various gradations of WordPress developer and the "pro" guys are a very competent and very pragmatic bunch.

- Most "pro" guys limit the number of plugins they use.

- They use ansible or similar for provisioning and deployment.

- They use sane theme frameworks like sage, timber or stem.

- They know how to do caching without using clunky caching plugins

- They try to adhere to 12-factor where possible

- They do their own devops

I mainly consider myself an iOS/Cocoa developer but I do my fair share of web development including WordPress. I even sell a pretty technical WordPress plugin (https://mediacloud.press). I don't recommend or choose WordPress because it's a great platform, but because it can be a solid pragmatic choice considering all things like time and budget and client experience.

But for the average joe, it sure provides plenty of ways to shoot yourself in the face. That said, what other options exist for them if Wix isn't enough?

Except a lot of MIDI in control type situations (lighting, user triggers) is run over ethernet these days. So if all things are equal on that front, OSC is a far superior design.

It almost doesn't even matter because outside of musical gear, OSC is becoming the established standard to control everything from DMX lighting to VJ software to OF/Cinder interactive installs to some more performance oriented software like Ableton Live (via LiveOSC).

I've written software MIDI sequencers (all the way back in the early 90's even) and you'll never be able to convince me MIDI is better than OSC.

Usually some type of creative interactive retail experience, anything from wall displays or projections that users can interact with to simple kiosks.

There are better protocols outside of MIDI like Open Sound Control aka OSC (http://opensoundcontrol.org)

I used to do a lot of experiential retailing experiences and OSC was our preferred control scheme.

This doesn't pass the smell test.

A lot of countries don't allow used electronics to be imported, which is more than you think.

Not to mention the duty you have to pay for the countries that do.

It's not a new dump:

https://twitter.com/wikileaks/status/1117123131804737541

As a parent of a T1D, statements like these are mildly infuriating. I'm sure you're joking, of course, but being resigned to some idea that you are going to develop type 2 at some point is lazy and lame.

Protein affects blood sugar too. General rule for type 1's is to bolus insulin 50% of the listed protein as carbs.

I don't agree with the parent poster's assertion either though.

Not even remotely true.

Actually, iOS will automagically load your xib for your view controllers at runtime.

- In the storyboard, delete the root view for the view controller.

- Create a new xib named the same as the view controller's class and that will get loaded without having to do anything additional.

Here's a quick example of what I'm talking about: https://github.com/jawngee/StoryboardWithXibs

Storyboards aren't a disaster, I think people's grasp of storyboard best practices is really the disaster.

For our team, storyboards are for flow and they are broken up into individual storyboards where possible. Individual xibs are used for views and view controllers. We don't put any UI in storyboards at all.

Autolayout is as easy or as hard as you want to make it. As with almost all things, less is more. I think people definitely need to have an a-ha moment with it.

I consider it a knock against you if you can't sort out interface builder or autolayout, if I'm being honest.

Except on iOS you get:

- Prompt to allow app to act like VPN

- Having to enter your passcode after said prompt

It's impossible for apps to MITM silently.

We implemented background removal in an iOS app recently. We went down a similar route, but ended up choosing a user directed grabcut (heavily modified).

It would be interesting to take the output of this and use the alpha mask as the starting point for the grabcut mask.

As someone (apparently the only one in this thread) that writes macOS and iOS apps, I can't wait for NSView and it's stupid lower-left cartesian coordinate system to die.

UIKit is so much better in so many ways, it's time NSView and its friends are all put out to pasture.

It's just Cocoa on macOS. Cocoa Touch is iOS (and tvOS and watchOS) and encompasses UIKit.

I depend on this machine to pay my rent, keep the lights on, keep insulin in my kid, keep us all fed.

If this machine bites the dust, I swap out the part or I restore from Time Machine. At least with this machine, I have the option of swapping out the part.

It's not some mystical black box. These are standard PC parts that are supported by macOS. I think I only use two kexts that aren't shipped with macOS to get to 100%.

If you stick to "standard" parts there is little to no risk. There is so much information out there on which parts are compatible and which aren't.

The hardest obstacle for me was sourcing some parts because they weren't available here in Vietnam. I had to fly to Singapore for most of it. Ironically, it was cheaper to do that for the parts I could get here, so everything worked out in the end.

That's why you wait a few days. The hackintosh community is very active.

Also, at this point, the things that would brick you in the past are no longer applicable with a modern hackintosh.

Houdini works on macOS.

Why not build a hackintosh?

I've got a beast of a rig that has been flawless. Easy upgrades (though you do have to wait a few days), handoff, continuity, thunderbolt all working 100%.

The only downtime I've had is restarts due to security updates.

https://pcpartpicker.com/list/JnJCf8