I have this with numbers (and consequently arithmetic). When I think of a number, in my mind I see its position in a never ending, wavy line of numbers that goes from left bottom to top right. This 'ribbon' of numbers kinda scales logarithmically and I can 'adjust my view' to 'look at' higher/lower numbers. Now that I think of it, I mostly use/see this ribbon when adding or subtracting numbers, not when multiplying or dividing.
Don't know if it's related but in one of my first classes as a kid (where we learned to count), we had some sort of banner on the wall that listed the number from 0 to 100. Maybe picked it up there.. Sometimes I also think this makes the more abstract math concepts harder for me to understand. If I can't visualize it, it won't stick (easily).
Asked some friends how they saw numbers, and they don't have anything like that. Wondering how this is for other people.
Wow. This rung a bell for me. I wouldn't have known how to put it so concisely, but this is exactly how numbers automatically reveal themselves to me visually when I'm considering them.
If only that extended to the size estimation part of my brain. I've gotten pretty okay at eyeballing kitchen measurements, but I'm completely useless at determining what will fit in the back of my car when shopping at Home Depot without a tape measure.
I've got a cursor in my head that I mentally move around and click and select things with. When I go insane, I'll probably experience somebody else moving my cursor around, instead of voices in my head.
I wonder if people used to think like typewriters, and heard a right margin bell as they thought, and then had to mentally hit carriage return every 87 characters before they could think any more...
I can report a similar visual. Mine isn't wavy, it's straight line from bottom left to top right in which each unit has a sort of notch division.
Aaaaand having to actually explain it seems to have completely messed the whole visual up. At this point I feel like I'm inventing a system based on childhood memories...
It does stretch back to my childhood though. I have strong memories of visualizing numbers in class, even specific problems like when we were asked to add all the numbers from 1 to 100. A problem in which I mentally drew half circles from 99 to 1, 98 to 2 and so on. I solved it almost instantly and thinking back I'm a little disappointed my teacher didn't investigate this more and help me explore this skill.
My internal number line exists as a ribbon of squares laying flat (i.e roughly parallel to the ground plane, although they exist floating in an infinite black space). From zero, it goes right to left, then turns around at 10 and goes back behind that line from left to right and then loops around again at 20 in front of the first line. Also, at this point the "camera" turns around following the line, such that it is now viewed behind the first line, going left to right. From there it proceeds in a straight line, with a slight incline, and then plateaus at 100.
Personally I don't miss it. IMHO the alpine image is perfect to run single services that don't have too much dependencies. On your host system you can use systemd to spin up these services as docker instances (if you don't need scheduling).
If only ads were an opt-in kinda deal (which with a blocker they of course are). I'd be happy to give you a short list of things I might be interested in if you'd stop tracking me.
You could call it a bluetooth enabled pedometer with integrated vibration motor, but that's of course not that marketing friendly.
(I'm guessing it does a bit more than the above?)
If you can do without the latest of the latest in Sass I highly recommend using a libsass implementation. So much faster than the Ruby version!
OT: I also like that they've used a BEM-like approach, although I personally prefer a double underscore as separator between elements.
Libsass is night & day vs Ruby Sass. No problems using libsass with Bourbon, Bourbon thankfully stays away from the bleeding-edge features (many of which can be emulated with clever functions).
In a previous project, we saw Sass compiles go from ~15s to about 400ms by moving to libsass. Completely changes the development cycle (with HMR or livereload) as you see changes immediately.
I've been using node-sass (libsass wrapper) recently, which hasn't been too bad compared to less (which is native to node/js). Seems to be working fine with bootstrap-sass, and surprisingly fast, compared to less, so I imaging the ruby sass implementation would be similarly slow by comparison.
I may be out of the loop here, but wasn't the big benefit of JavaScript everywhere that it's the same JavaScript everywhere?
Does it matter if server-side is JavaScript Next Gen and browsers lag by a few years of features?
Too many more iterations of this and you'll be back to two programming languages again and web developers heads will explode from having to learn two things instead of one things.
It's been "the same javascript everywhere" mostly due to the ECMAScript group kinda stalling for the past 15 years. The stabilisation created through that has been useful, but the plan is to transition the spec onto a one-year update cycle.
That means that going forward we'll likely have more feature mismatch between engines, making backward compatibility compilers pretty important.
Chrome (logically) already supports features of the new JS spec that 'only now' get put into node.
With automatic updates for browser being the trend currently I also think that it is now easier to keep the server and browser support for JS in sync.
Not necessarily. I don't think the v8 team really consider the Node project so breaking changes in v8 take some time to get merged into Node/io.js. This is the reason that arrow functions are only shipping now when v8 marked them complete a while back. AFAIK Node is somewhere around 3+ months behind Chrome.
V8 has had arrow functions for a long time, but until recently they were not fully spec compliant. That is also why iojs put them behind a flag (separate from the flag that enabled stable harmony features).
Yeah, 'ship' means different things in different contexts. In the context of your original comment, node stable is getting arrow functions within a week of Chrome stable getting them.
In general, io.js has been very good at picking up stable V8 soon after it ships in Chrome. The exception was V8 4.3, which was not picked up because of API compatibility issues.
This is not a problem for Chrome because chrome doesn't expose the V8 C++ API to large body of third party module writers like Node does. It takes time to deal with some API changes.
Unless one of the passengers knocks out the driver while bouncing around in the car..
The argument mentioned by tghw is the only reason I agree with the law on this point. Considering law's meant to protect people from themselves (and only themselves) in general I'd pick freedom over mandatory safety any day.
We run some shops at Byte and were able to quickly apply the patches back in February. This week we got an e-mail from a worried customer who got a message in the back-end (from Magento) that his site might be vulnerable: 2 month's later..
Personally I've never liked Magento much; it needs expensive hosting even for modest shops and seems to be bloated with functionality you never use. And in the end you always end up with writing a bunch of custom modules because the Magento way is never your way.
Don't know if it's related but in one of my first classes as a kid (where we learned to count), we had some sort of banner on the wall that listed the number from 0 to 100. Maybe picked it up there.. Sometimes I also think this makes the more abstract math concepts harder for me to understand. If I can't visualize it, it won't stick (easily).
Asked some friends how they saw numbers, and they don't have anything like that. Wondering how this is for other people.