pixelbash

Try two way binding on nested form elements with jQuery.

Given the historical frequency of war, I'd say what looks like stability probably isn't as stable as one might like to assume.

Object fit polyfills were iffy at best last I checked, though that only matters for IE11 (and Edge if using a non img tag).

That would happen if you cloned one person a million times, but with all the tradeoffs of genetics I doubt there even is a single conclusion to be reached

Even if they were doing that now, won't it be around 20 years before it started having a large impact?

Bit of a straw man isn't that? Your one single cell phone is a bit different from one of hundreds of prototypes not owned by anyone in particular or even intended for sale.

> I don't think its impossible that this flea market could become a hipster hang out

Reminds me of Camden market

> Traditionally, the publishers accept papers for publication for free but charge steep subscription fees

To my knowledge (academic family and partner in NZ) this is false, publishers charge for both publication _and_ reading in general.

Without leaning one way or the other I've always wondered what neuroimaging one of these experiences would look like. If nothing obvious is happening and the imagee reports a rich and detailed experience it might be persuasive.

I could see it even driving migration out of cities. One of the big reasons for not already doing so is the terrible connections for remote workers further out.

Where it can be done with H5 and CSS3 we use those things, we don't invite complexity for the sake of it, but it's really very easy to run into the limitations of CSS3 when doing something even slightly unusual.

Vue replaces the dom of wherever the app is, so the choice is between having everything within a single app div or having a ton of apps talking to each other. Given that the ton of apps solution still breaks fairly essential functionality (for online shopping) and requires a fair amount more structure it's a bit hard to see the benefits.

The dynamic dom frameworks (and webpacks) have a tendency to encourage moving everything into javascript. Generally this means that enabling gradual degredation requires building most things twice, once in static form and again for when vue et al have been loaded. Separating the two takes significant time and effort, which also introduces extra surface area for bugs and odd interactions. It is expensive to build this way, and there are other things worth prioritising.

Ultimately all website are optimised for their target audience, if 30% of our users used IE6 then we would (sadly) target that. If users value ease of use on a baseline browser then that is prioritised, and if static information and nojs turned out to be what most users valued highly then we would do that too.

Also before someone mentions it, I am using SSR where possible so at least something displays, it doesn't make one of these websites function well without js though.

I feel like I'm going to be in a huge minority here but I am one of those developers that builds websites that won't load without js. Hear me out though.

I primarily work with ecom, and we build highly dynamic sites in an increasingly rapid arms race for engaging design.

Before vue I worked with jQuery like everyone else, controlling the dom manually to react to changes in application state. Those were dark days.

Now I can manage the cart state and increasingly everything else over apis and have the application display all these updates in real time, along with all the whizz bang the design team decides is flavour of the week. All in not much more time than jQuery and basic layouts previously took.

So, sorry if my site doesn't load without JS, but it's not about the ads. The web isn't just document display anymore, everything is an app.

At a guess the USA is not the primary market for Lexus.

I'd call it an analogy rather than a straw man. The formula is [now thing] is safe in [now context] but [future context] != [now context] so is [future thing] safe?

It's fair to say my concern is potential abuse of any system in a fluctuating context.

And apparently being able to add new features without "breaking the world"

I think the issue here is not where we are at but the risks inherent.

It would be entirely possible to have a benevolent dictator, he might think he is doing everything for the benefit of the people - and he might even be right. This situation is fine, the issue is what happens when that dictator dies.

Similarly with mass surveillance, if used with restraint and for the right reasons it could be completely fine. The problem is what happens if the situation changes, there is now a massively powerful tool available with little recourse for change.

I think the issue is not the situation as it is _now_, it's the risk potential it inherently has that is terrifying.

That's where I am on this. Before nesting I had to take great care to avoid conflicts. I guess this is what BEM set out to solve, but it seems to have limitations.

An approach I use is to try and build something in css first, if I can't find a way to make it work then I'll break out the JavaScript.

Css is surprisingly good in places, but it also drives me up the wall as soon as I let myself expect to be able to do more things in it. Yesterday it was gradient masks.

Even adults need mentors

Shouldn't that be (s/more/less/)?

Not everyone works the same way. For example, consensus is that you should have at least 8 hours a sleep at night. A fairly large chunk of 'successful' people need &/or get a lot less than that. If I try that kind of schedule I am a zombie within a few days.

Shared profit can negate shared costs, particularly those brought on by systemic issues that need solving or individuals that didn't do so well in the health/job/birth/intelligence/etc lottery.

Or would you rather a non-society where everyone fends for themselves?

About the insulation thing, to be clear, it's just a heat pump and a certain R number in the floor and ceiling (correct me if I'm wrong). Pumps cost <5k to install and insulation isn't that much more if done while building. Double glazing isn't mandatory either.

What I'm trying to say is walking into a house here in winter still doesn't feel like a place in say, Northern Europe. I don't think it's that onerous.

Sources: Partners brother in law is a builder, parents just had heat pumps installed, our landlord just installed underfloor insulation and it's currently 12 degrees C in the house.

Our rent: 700NZD pw

Our calculated repayment on a 20 year mortgage with a 300k down payment on the estimated CV of this house: $1370 NZD pw

Yep!

This is okay as long as you are in one of the locations where mortgage is roughly equal to rent. In some places it’s closer to double, unless you want a 100 year mortgage.

Well it does mean in order to understand the library and/or contribute you have to use <flavour of the month>. Also it makes the library prone to rewrites if something else comes up. I don’t mind TS (though es6 suits me fine) but I have seen many js paradigms come and go. Who knows maybe TS will stick around for the long haul.

Re the second point did you manage to get around this? Played with it a bit and it felt almost like flash back in the day where you could eschew the timeline and do everything programmatically. In the end ran into a problem where I wanted to move the universe around the player and couldn’t get the particle engine to cope..

What information do they have access to?

I do think a simulated reaction time or limited actions per second might be more fair, if they don’t have that already..