adamcw

SPA's tend to come with build systems, but that is just a side effect of their complexity. You can have a front-end build system independent of SPA/MPA architecture. In fact, you should, at least for minification and whatnot. That system can add a content hash or some other strategy to force invalidation at build time for deployed artifacts. Barring that, whatever is serving the asset should handle it's caching/TTL stuff correctly, but config of that can be hard (in complexity or domain knowledge.) Build hashes have been the most resilient approach that I've found so far. Mostly because it is easily automated in artifact generation.

Not a binary thing, no. But who gets to be in charge of that speech? Do you trust them? Do you trust who will follow them in power?

Where I live, I'm vastly outnumbered by people who have vastly different values than me. Their party is in control now. Pretty scary to think they could shut off my voice at whim, or worse.

Not allowing information to exist, regardless of intent or how it's perceived as "good", is an authoritarian act in and of itself. It will only polarize those that feed on it.

It's the "let's burn books" mindset, which is just a bad tactic. Misinformation in the modern(or any) age can't be fought that way. The internet is good at amplifying that which people seek to censor. I hope we can agree this is good for positive ideas, but the mechanism employed doesn't care how "good" you find the idea.

And to be entirely clear: I think the subject matter at hand is abhorrent. Fascism feeds on censorship. It doesn't hurt that side, it helps them control the narrative.

I think most of my concerns center around this being an impulsive stream of clearly stress based posts. I think a lot of really good conversation could have been raised, which I fear may be lost by a) the stream of conscious nature of the posts, and b) a lack of better editing or personal judgement on a bit of the content.

The frustration shines through, but so does a lot of "advice" about dealing with an unhealthy culture in an even more unhealthy way.

I wish the author the best, the little I know of his past work seems solid. I commend raising these issues, but it raises a few red flags with me in the manner of execution.

I would also like to echo this question, always interested in what people listen to while working.

While discussing the Node C binding architecture, I think it's also worth noting The Neon Project* which is extending that lower level binding system into the Rust ecosystem. I'm not personally involved in the project, but I think it has a lot of potential.

* https://www.neon-bindings.com/

Hahah. Nothing to be sorry for, I was just curious. There are enough source systems out there, I wouldn't be surprised if they were a few I hadn't heard of.

As I'm not familiar with those, I have to ask: did you mean CVS and SVN?

PSA: If you are using a DisplayLink based device, this update will break your setup. They have a beta driver on their site that will re-enable clone mode, but not extended desktops, etc. Through the 10.13.4 beta the rumor was that changes to support eGPU's broke something they relied on.

Edit: 1.0.13.4 is not a version of macOS.

This is not a response to your post in general, however it is "Berners-Lee" not "Burners-Lee" as your own sources will confirm.

I think they got that, but customers can be difficult and the impulse to launch them can be strong.

Thank you for your helpfulness, regardless.

That's odd criteria.

Mind passing those resumes this way?

Laying off employees due to revenue concerns has been something I've seen, but I've never seen an individuals salary cut. I would leave somewhere that did that in a hurry, if I had the option.

I'd find the timing scarier if the beta for 9.3 hadn't been going for a while before this all came up, and we were already right around the number of releases they always do before an GM build is ready.

This is what I came to suggest as well. I would also say that Express is a good one as well if you're looking to learn Node. Not quite as clear as the annotated source for Backbone, but well commented.

I also liked the "Let's Make a Framework" posts at DailyJS. DailyJS in general was a great blog that is now closed, but the archives are still up.

https://github.com/strongloop/express

http://dailyjs.com/framework-index/

Noted, but I'd argue that contributing to existing open source projects is better for the general populace than reinventing wheels.

I'd consider Webkit pretty useful.

Is there an argument that hibernate is harmful? I hadn't heard that one.

It's certainly useful, but I think the comment you were replying to was thinking more along the lines of saving that state without doing all the work our computers have to do to go into hibernate.

I for one would love a faster and less error prone sleep/hibernate feature. (Although recent Mac OS implementations have really cut down on the error prone part of that. I'm not sure where the Linux/Windows crowd is on that, I would assume the story is the same/similar.)

The app looks awesome, and also served as my introduction to Hype Machine. How I haven't managed to hear of this service before is beyond me. Now I'm just sad I didn't know it existed until now.

Also great to hear that Swift development is going smoothly. I just started into learning it, and so far the strangest thing I've found is that I've learned a ton of Objective C by having to struggle through missing documentation/examples and having to learn the Obj C way of doing things and then translating them to Swift. It's been interesting.

Things currently heavy in my rotation (in the format of Band : Album(s)):

  - Murder By Death : Bitter Drink, Bitter Moon, Red of Tooth and Claw
  - Strike Anywhere : Exit English
  - AFI : Burials
  - Circa Survive : Blue Sky Noise
  - The Raveonettes : In and Out of Control

I had no idea such a genre existed, and I think you've just made my day. Thank you for this.

In one of their public statements, they've indicated that the new app will be able to import/open Aperture/iPhoto libraries.

Hopefully the implementation is fairly seamless.

This is the only one I've seen: http://d35lb3dl296zwu.cloudfront.net/uploads/photo/image/162...

It was linked in The Verge's live blog.

The beta is already available to download from the iOS/Mac dev center.

There are build instructions for Linux and I think even Windows as well. I think Ubuntu is currently the main target on the linux side.

Edit: Just double checked and there are Windows build instructions at https://github.com/atom/atom. Although I haven't actually tried to follow them, so I'm not sure if they end in a usable build.

Also, in my personal experience, "I don't know" is a valid answer to those types of questions, as long as it is followed by an explanation of what your methodology would be to fill that gap.

Show stopper for me as well. I wanted to see if they had any projects that would be fun for a night/weekend type thing, but they are asking a lot of info without giving enough back to make me feel comfortable sharing.

There are quite a few places in the code where it appears the author took a longer way around than is necessary, which upped the line count a bit.

An example of this would be restating the DOM tagName on each view instantiation. This appeared to also be done with the className, which didn't appear to change (Although I admit I didn't look particularly hard).

There were some other areas that looked like they could be optimized by removing unnecessary glue. The render function in PhonesFilterView looks to be doing a lot of work to choose the selected option. Unless I'm reading it wrong, you could just pass in this.model.get('sortBy') to the JST and let it do the comparison to select the correct value. Quick value compare instead of a model compare.

I appreciate the work that goes into these types of comparisons, I'm still lead to believe that it shows more about how well you know a framework than it does about the framework itself.

Thanks for posting OP, it was an interesting exercise.

Neither did I.

Now to decide if I: a) Comment more b) Throw down some custom css and get the feature on my own.

Bandwidth concerns cut both ways. I typically worry less about my server being able to serve it, than I do about the client having to receive it.

For desktop users it's less of an issue, but site size matters a great deal to mobile users.

At least that's where I tend to worry about it, not sure if this is the common reason.