hlfcoding

Subpoena?

Here's my specific use case: https://li.st/hlfcoding/instapaper-impressions-4vENbtbDKLetv...

Apple definitely seems to have a larger software surface area than hardware, where they tend to discontinue more frequently. Keep in mind the companies Godin compares it to are focused on web services and only have one user-facing product. It's an unfair comparison. Apple provides some of the best developer tools and APIs. An essential software suite that just works is what I'm looking for, and for the most part it's delivered.

I clicked for a deep dive. Not what I expected.

I can really identify with this:

"Once you know about all the ways that skimmer thieves are coming up with to fleece the banks and consumers, it’s difficult not to go through life seeing every ATM as a potential zombie threat — banging and pulling on the poor machines and half expecting half hoping parts to come unglued. I’m always disappointed, but it hasn’t stopped me all the same."

And I currently practice this:

"Lastly but most importantly, covering the PIN pad with your hand defeats the hidden camera from capturing your PIN — and hidden cameras are used on the vast majority of the more than three dozen ATM skimming incidents that I’ve covered here."

Very interesting technique:

  .r3z-hide, .r3z-hide * {
    color: lightgrey !important;
    text-decoration: none !important;
    font-family: redacted_scriptbold !important;
  }

Duplicate of https://news.ycombinator.com/item?id=11347006, where the discussion is, although this appears to be the earlier post.

If you look at NSHipster and other sources in the iOS community converting their code samples to Swift only months after its initial release in 2014, it says something about the pent-up demand for a nicer language than ObjC. Plus Swift seems to be designed for ObjC devs to have an easy transition, although slightly less dynamic (and unsafe).

Demand for iOS development could be tapering due to app market saturation; saw a post recently around here about that.

The variety is interesting, especially the few where there were no computer or tablet.

Neat countdown animation.

This is great news, at least better than proposing a giant vent system.

"I use to be cool, but then what was cool got weird..." Judgy article.

— not &mash;

Honestly why? Will you make that many desktop apps that are all the same?

That's truly surprising. I don't recall Facebook ever resorting to layoffs?

I'm glad I stopped loading the page.

I believe the project is called Utron. I'm also not sure how a 'database-driven web app' differs from web apps in general?

I wonder how restaurants factor into that, especially fast food. Any place that preemptively prepares food is very likely to waste a lot of it. Having worked at an am/pm for my first job, I was blown away by how much food is thrown out after 3 hrs from when it was cooked.

This looks useful as an opt-in performance feature.

An unordered list of missing features from me:

- No ability to store the tab size setting. While appending '?ts=2' to the url is ok, it's not convenient and usable on a daily basis. The same for omitting whitespace changes in a diff / pr ('?ws=1').

- No ability to step through history on a single file while in blob view, or blame view. In blame view, the commit link goes to the commit, not the blame of the file at that commit.

- Agree with OP that notifications need to be grouped / summarized better. Perhaps expandable summary items per repo per type. This is mostly useful for private, work-related repos. Pulse and notifications are basically the same thing.

- Stars cannot be tagged. This makes managing hundreds of stars difficult. There's apps like Astral, but even those are lacking.

The irony is implementing progressive enhancement and accessibility is anything but simple, and probably just as big a maintenance burden as custom form controls, and comes with debatable gain.

Each project and team and project is different, there's no constant requirements in frontend, in tools or features. Some teams may be super unproductive without Sass. This post is very much written from the bias of older trends, and from a time when the frontend had fewer real concerns other than styling a document.

Re. civility, I've had very good results in reducing stress between both parties by clearly separating the defects in the work from the person / people involved. I think that's the key because I've had terrible experiences when that did not happen, when I was either blaming or blamed (seemingly) by teammates personally for any mistakes. Still, I'd rather receive any honest feedback than none at all, even if it is presented incorrectly and callous. Holding back feedback to be nice can grow problems and erode trust.

Their iOS app[1] looks promising, but the reviews seem to indicate it's still not there yet. Back in 2004, I had friends who grew addicted to casual browsing of Wikipedia in the browser. I'm not sure if that activity translates well to mobile browsers, but that it's probably a variety of factors: lack of integration with the device OS, longer average latency, more user actions to navigate content (accordion interface). As far as editing, not having input accessories for the markup syntax makes editing on mobile painful. Luckily, these problems all seem surmountable.

[1] https://itunes.apple.com/us/app/wikipedia-mobile/id324715238...

See http://hlfcoding.github.io/hlf-jquery for an example of the template in action.

This coming from a guy whose website hadn't been made responsive.

Goes to show 'password' is a total misnomer that encourages bad security practice.

Apple's website is just getting worse and worse...

This is pretty nice. Great job. Drag-n-drop to tag is nice.

Some feature requests:

- Keyboard shortcuts, especially for tagging.

- Alternate layout that supports narrow window widths, much like email clients (Mail.app).

- Resizable / collapsible sidebar.

- Sortable tags list.

Don't you mean CMS?

Decent overview of the past two decades. But it's ironic the navigation and decoration on that site are also great examples of bad web design.