Profile

Cover photo
Morgaine Fowle (de la faye)
Lives in Washington, DC
304 followers|280,872 views
AboutPostsPhotosVideos

Stream

 
Flux implementations often only allow one action to be dispatched at a time- actions can't call other actions. I'm not sure what this limitation is to guard against. I feel like there's an update queue, an outstanding update process, that when fully terminates/clears (coroutines all finish) can let updates happen.

Simmering it down, perhaps this is loser to Cycle.js?
http://cycle.js.org/getting-started.html
A fully reactive JavaScript framework for Human-Computer Interaction
1
Add a comment...
 
My burning the midnight oil is running these flashlights low. I place them around the room for some shifting ambiance.

Last night was pretty shocking. One light was dim dim dim before I emerged my head from the unspeakable npm committing I was doing. Samsung 25R's (18650's) in these guys- these are supposed to be indomitable batteries but that was absolutely one crushed battery. I was too tired to put the voltage meter to it, but 2V? Yeah maybe.

Charged back up over night, seems to be discharging ok today. I have four batteries I use for this purpose, all marked with an X because this sort of thing happens, it's only a matter of time before the abuse really catches up.

I've wanted to build a battery charger that also tracks individual cells charge over time, and can do some discharging too. NFC tags on batteries that gets swiped in to remember the previous profile. I want to see how injured these batteries are from this burning low the midnight electron.
1
Add a comment...
 
Brace yourself, a meteor is coming
http://i.memecaptain.com/gend_images/F7qYsQ.jpg
Via work, and projects and things.

Recently, Meteor, the maintenance burden forcing its way into a hundred thousand projects,
https://plus.google.com/113218107235105855584/posts/HqP7qZHPjei
1
Add a comment...
 
AMD has gone for the bare minimum in FP64 performance that their architecture allows, leading to a 1/16 FP64 rate on Fiji. This is a significant departure from Hawaii, which implemented native support for ½ rate, and on consumer parts offered a handicapped 1/8 rate.
http://www.anandtech.com/show/9390/the-amd-radeon-r9-fury-x-review/3
Egads. I guess I better stop imagining we'll have spare FP64 to throw at large-scale scene-building or precise shading.
1
Add a comment...
 
We can only begin to talk about stories like Uber when we understand the mechanisms of market and exchange. So let's take a smaller case- if I want to send someone I'm chatting with my phone number and a webpage, what options are there, what can I do to make a deliberate exchange with this person? If I want to advertise to anyone in the area that I'm an available ride, what broadcast channels are available? If I want to provide a review of the rides I take, how can I broadcast those reviews?

Even the basic case is dire- our most basic communication patterns are deeply intermediated. We're just beginning to see services like FireChat emerge, but they remain deeply proprietary, closed systems of exchange. Although we have emerged recent means of networking- BLE, Wifi-Direct/wifi-p2p About the only standards based communication system that doesn't rely on deeply centralized highly controlled systems is Physical Web, and it's maximum capability right now is "here is a url".
https://github.com/google/physical-web

Which is kind of ok. Once there is an transport protocol- HTTP- advertised and talk-with-able, the followup questions of what to communicate can be defined in that lowest level, transport permitting. The next step is doing something with the endpoint. Host-meta and json-home specs begin that by enumerating what is happening, what resources are available on an endpoint. This mirrors the network endpoints advertising their availability- here the web services advertise their availability,
https://tools.ietf.org/html/rfc6415
http://tools.ietf.org/html/draft-nottingham-json-home-02

This is the beginnings of us people's communication. This is where we start, where we can begin to talk with each other. Whether these services we talk across retain the present api mold- client/service based, deeply consumeristic and self-centric, or whether we begin to blow up that mold- with general data interchanges, ambient data, web-hook oriented, self-hosted and delegation-hosted persona systems... whether we build apps/systems or specs, whether we keep building specific systems/specs, or whether we build general systems/specs, and whether or not those systems are client/server centric or interconnective/intertwingular... these are the remaining pushes that describe how, from the ability to communicate, we grow as communicating beings.

Recently, growing the user-agent web,
https://plus.google.com/113218107235105855584/posts/HhT5wjAUCZo
physical-web - The Physical Web: walk up and use anything
1
Erik Corry's profile photo
 
Interesting perspective.  I'm not sure how to get from where we are to where you want to be.  Exhortations to the technorati to support open systems feel unlikely to move the needle much.

The communication systems we have that don't feel heavily intermediated are the web and the plain old phone system.  The web is unique. In the case of the worldwide phone network, that didn't just happen: There was a concerted effort on the part of regulators to demand interoperability - an effort that we haven't seen carried over to the modern world.  An obvious modern analogue would be legally required chat interoperability, but in the Internet age, the authorities seem to be asleep at the wheel (FTC) or attempting power grabs that benefit the censors and the entrenched power structures in countries lacking freedom (ITU).

But even if the regulators threw themselves into the breach for non-siloed interoperability, this falls far short of the sort of organic, federated, yet high functioning communication that you are imagining. Phone systems and chat protocols feel too simple with little chance of emergent complexity, while the web is fairly low level and with no built-in P2P framework.

Just one of the issues with going beyond this is the handling of malicious actors, spam and abuse. The web appears unmediated, but there are filters of surprising complexity and sophistication that protect ordinary users from the darker sides. Many users are not able to recognize even the most blatant phishing scams and would be lost if nobody was intermediating their communication at all.
Add a comment...
 
Dear Russia: you are cowards, get a grip, stop trying to deliberately cause plane crashes. This is the most cowardly, it is unfathomably hostility seeking, it is madness in it's demonstration how rogue an entity can go in deliberately shaking the world's peace. Stop, you cowards, stop,
It’s not clear that NATO has a strategy for dealing with these everyday provocations.
http://www.nybooks.com/blogs/nyrblog/2015/may/14/russia-nato-twenty-feet-from-war/
http://www.vox.com/2015/6/29/8845913/russia-war
On April 7, a war between Russia and NATO forces defending the three Baltic republics was avoided by just twenty feet.
1
Alex Bravo's profile photo
 
And calling a large nation a coward three times is not shaking the world peace?
Add a comment...
In his circles
1,171 people
Have him in circles
304 people
William Bishop's profile photo
Mike Amundsen's profile photo
Marcus Griep's profile photo
James Body's profile photo
Steve Nagy's profile photo
Jed Koch's profile photo
Kendall Clark's profile photo
Ralf Laemmel's profile photo
Tom Gundersen's profile photo

Communities

30 communities
 
TypeScript is at least trying to be a viable reflective language, to be able to serialize the type-information they've been implicitly coding up.
I guess lot could be learned from type erasure mistakes in Java.
https://github.com/Microsoft/TypeScript/issues/3015

So here's the current state of affairs on that-
https://gist.github.com/rbuckton/4b8df4908aad49aac212

There seems to be almost no interest in taking data-objects (incoming JSON) and enriching them. Everyone is in the fray building super-powerful boring Java-esque OO, reinventing annotations and decorators. Even StampIt, one of the more-sensible/less-Java JavaScript class-construction kits ignores what I think of as JavaScript's base case- can I take this object that I already have, and apply some sensible upgrades.

Not sure what classification to apply; 'Java' is a stand-in for boring, unflexible type-system that makes the language designers nod and smile: no one will ever be able to do anything at all untoward with this! they say, patting themselves on the back.

AtScript at least pointed out that the type information probably should be shown in the runtime. I don't think TypeScript would have noticed they were building only for compile time otherwise. I'm glad it's here, but I don't think it's anywhere near the flexibility and mungeability that JavaScript really expresses, and it's a frightful engine and stricture to emplace, with a fairly complex, deeply untried & untested series of speculative language features atop (Decorators) keeping the thing pointed somewhat in the Java direction. That type-serializability, that the type information as a thing hasn't been considered shows who and where this monstrous tool chain is for.

Is it any wonder that Facebook just broke free and wrote their own schema language, and their own query language for #GraphQL? It''s ridiculous to me that they invented two languages, but they at least didn't impose a vision for JavaScript by placing these innovations in their own scope and own forms.
1
Morgaine Fowle (de la faye)'s profile photo
2 comments
Add a comment...
 
SnappyStart is an interesting competitor/alternate implementation to +CRIU. It does a good job stating the Checkpoint/Restore case:
Faster startup, if the program does a non-trivial amount of computation during startup.
Saving memory, because memory pages that the program writes to during startup will be shared between the instances.
https://github.com/google/snappy-start

Containers <<< Snapshots, easy as that. Building stable images is something we can do directly. We don't have to keep rerunning our processes from scratch every time, we don't have to craft containers to allow recreation of the environment.

Some of snappy-start's advantages we can eek out in other fashions- Java Class Data Sharing allows us to rebundle the core package Java will always boot with, packing in application libraries we know will be commonly used: this is Java's neat trick to allow sharing of libraries. Snapshotting can go even further- it's not just class structures that get loaded during startup that get shared, it's the initialization of static elements of libraries, and first bootup of the app that can be mapped from some shared, read-only mappable-files.

Recently, CDS,
https://plus.google.com/113218107235105855584/posts/K9seVudjaiU
snappy-start - Tool for launching a Linux process from a snapshot
1
Add a comment...
 
Celebrate! A better running world, for some world hosters.
https://www.compose.io/articles/coming-in-postgresql-9-5/
With PostgreSQL 9.5 just released as an alpha (and betas from August till its ready) the new feature list for the next version of the SQL database has
1
Add a comment...
 
The idea of "growing" a company is terrifying to most engineers. They rarely see a company able to deliver itself value as the bounds grow. The engineer lusts for axemen running the show- all the cultural issues are subordinate to identifying with a ruthless technical leader bent only on getting good results out of what can be brought together. Most of the code-process is non-value, but lose the scent, and the project is lost. Most of the architecture could be built any of a dozen ways, but fail to track your inquest in towards your domain and you'll spiral out of control without it.

Everything knowable, put tightly into place, guided with precision- that's the culture where the developer understands just how strongly they do come to rectify what situation it is they work on. We want hard work, work that demands correctness, that, if we did it any other way, everyone would know, and jump on it or lay that piece to rest.
1
Add a comment...
 
OpenWRT's namesake WRT54G was a Broadcom platform, but it was basically Atheros/Madwifi->ath that set the enthusiasts on fire, that were good enough to serve, that came with good virtual (multiple) access-point support (or access point + other mode).

Here in 2015, Ath10k is heading back towards blobs, 802.11ac support is (across all boards) infantile/not being done in upstream/barely possible on usb (hope you like old kernel versions!). How do we turn back these kinds of losses, how do we make sure we can keep running modern general purpose systems?
1
Arnd Bergmann's profile photo
 
There is some hope that MTK could be the next platform of choice. Not quite there yet, but at least I heard the data path in mt76 is blob-free, unlike bcm47602 and qca9980.
Add a comment...
 
Unix sockets are all well and good, but they cannot be mapped across- one ought use a tmpfs space or pass the new memfd's around to get their zero copy from communicability to usability- question #2 is what framing does one use to send http messages without needing to reparse? When do we serialize as protobufs, &c, as we memfd our http messages among the core-clusters?

Anyways, a good start none-the-less with one of the fast C http servers doing 1.1 over unix sockets,
https://github.com/h2o/h2o/pull/383

Recently,
https://twitter.com/rektide/status/614119730572566528
Some application servers speaking HTTP/1.1 is capable of listening to an unix-domain socket (which is often faster and easier to operate than TCP sockets). This PR add to the proxy implementation ...
1
Add a comment...
People
In his circles
1,171 people
Have him in circles
304 people
William Bishop's profile photo
Mike Amundsen's profile photo
Marcus Griep's profile photo
James Body's profile photo
Steve Nagy's profile photo
Jed Koch's profile photo
Kendall Clark's profile photo
Ralf Laemmel's profile photo
Tom Gundersen's profile photo
Communities
30 communities
Places
Map of the places this user has livedMap of the places this user has livedMap of the places this user has lived
Currently
Washington, DC
Previously
Denver Colorado, Summit County Colorado, Portland Maine - Maine - Ars Orbital HQ, Feythabolis
Story
Tagline
fledgling immortal
Introduction
just your average dj savior
Work
Occupation
fledgling immortal
Employment
  • fledgling immortal, present
Basic Information
Gender
Male
Other names
rektide, rektide de la faye, lightbringer, unregistered artificial virtual construct, boy, stabby mcstabington, your vast reverence, awakener, m. fowle