barrystaes

Why cant you use it yet?

I only tried a few XP-era programs, but so far they work fine out of the box. Including a Win32 application i've developed myself.

> and it rationalizing everything down to its core isn't necessarily helpful.

Its why i promised myself to never try and understand how cars work. They just work.

If only i could apply that to just about anything..

> Our tolerance is typically within 1-12 frames (and a bunch of other requirements around shot changes, etc.)

Tell me more!

> Is a shared database in microservices actually an anti-pattern?

No, unless you dont want (or care about having) a single source of truth. If state is distributed its harder to backup/restore/rewind or even query atomically and reproducibly.

You could still make the single database sharded and duplicated though, but still: in most cases its still one shared database. Even storing Files outside of a DB is just sharding, important thing is the DB refers to the file and still is the single source of truth.

And when you want vertical segmentation see designs like multi-tenant, but its still not a database per microsevice: quite the opposite.

When you dont want a single source of truth you could do without it ofcourse.

Does something like flightradar24 exist for trains?

The only API i found exclude all freight trains. (Netherlands) https://spoorkaart.mwnn.nl/

Hmm.. the Google article stipulates:

> WebAssembly on the other hand is built entirely around raw execution speed. So if we want fast, predictable performance across browsers for code like this, WebAssembly can help.

So i wanted to see how i could use WebAssembly in a React webapps. I found this SO question sees the opposite:

> When running this [ WebAssembly] code in Chrome, I observe "pauses" that cause the app to be a bit jittery. Running the app in Firefox is a lot faster and smoother.

https://stackoverflow.com/questions/53584607/react-app-with-...

Same code, different browser, different performance. I'd love seeing a Google Developer answering that question in depth..

> A bet in which you can win nothing more than a refined résumé, or lose a lot of time.

I strongly disagree. Perhaps if you dont really have a problem that needs React to solve it. I understand you already had extensive expertise solving this problem in JS without React et all.

> Personally if you are spending all that time and energy recreating the wheel just to say "you don't use JQuery "

Heavy movie trailer voice Consider a world, where there is no problem that required jQuery.

I refer to React and such.

Well the library looks good enough to give this a spin. And a demo on http://todomvc.com/ JS labs perhaps.

The article is on a suspect domain:

  https://https.www.google.com.tedunangst.com/flak/post/griping-about-go

Is there any legit reason to have https.www.google.com in there?

To avoid having to update these files on your pc, these could be served by a "server" on the internet. We would have to run cables around the earth so everyone can benefit.

> No one taught me to code.

As a kid i learned to code using an old book i found, with a computer but no compiler:

I simply had not figured out that EDIT.COM was not QuickBasic. Looks the same but had no Run menu... if only somebody told me! As a kid i could use a teacher.. as a knowledgebase to query, not necessarily as a teacher.

It was fun to run what i wrote before, once i figured that out though.

Not much later i found out how to delete files..

Exactly my thought. I wont be using this for exposed/public access. Which websockets are.

First vector that comes to mind the stdin escape sequences, then there is the inevitable leaking of sensitive information (besides bugs in the process, what about its unhandled exceptions, segfaults, or other system errors), and then there is the denial-of-service unless it can throttle before invoking a process, and lets not forget about command injection.

But still i must say the idea is nice in simplicity..

Adding to whats already said in other replies:

Plus:

* is it tech i wanted before i knew it existed.

* tech clear on limitations / being unfit for case XYZ.

* community with low frustration levels.. where clear answers get clear questions.

Con:

* tech that is just the opinionated alternative of the month. Even if it catched on.

* tech website cant (or forgets to) explain solved problem in simple laymans terms.

* not actively maintained, must if facing external dependencies. (includes os, browsers, libraries, etc)

* docs are inconsistent/unversioned, or old versions are not kept available.

> Egeria is in-memory for performance reasons I dont see how this relates, as a relational DB can run in-memory, and overflow to SSD. And cache values for the "views".

Install a webserver/application? Sounds like what you want is a tiny Dockerfile. Can highly advise giving this a try, PM me for questions.

And if written in a script (or non-compiled language) probably something to keep your source safe and avoid abuse. Some random examples are sourceguardian (PHP) or proguard (JAVA) or enclosejs (Javascript)

> Anyone else experience this? Got any tips?

Sometimes. Some things i do to ensure correct question-answer contexts:

- When in a meeting with (loud person pushing) wrong answers, ask the right questions.

- People dont understand the answer if they dont understand the question.

- Use the above to give the obvious correct solution within their context.

> it seems to focus more about the benefits of having a centralized request broker / gateway for your APIs

Exactly my thought. From article, about REST API:

> Any API change had to be deployed simultaneously to all services using that API to avoid downtime, which often went wrong and resulted in long release cycles. Using GraphQL in a single API gateway, we would simplify the service landscape drastically.

Atom was a great experiement to find the limits of the innovative design now known as Electron.

They succeeded: the limits where found, moved, found again, moved again, and now hidden far away. The current limit is just performance. Electron is the valueable outcome, in hindside Atom was the side product.

I dont use either! Simple text editor = nano + notepad, and IDE = JetBrains (mostly WebStorm).

> a simple, easy-to-install option for server-side software > would unlock countless opportunities for developers.

Docker. Its how any software can be packaged with its dependencies. Best for linux serverside/webapp software.

Install and run a docker with one console command, just provide a network-port and folder mapping.

Or use a webinterface, i like how Unraid does this. If you have a old server/PC to spare, definitely try Unraid.net by just booting it from USB stick.

Do you know of Unraid? Webinterface for NAS and installing dockers in just a few clicks. Simple and versatile. And no need for raid shenanigans - hence the name.

For getting started with dockers on your home server, try Unraid OS. Its terrific and takes all the pain away. I consider myself a docker power user now, but i still use Unraid at home because it works great.

I like the shallow copy, and never needed a deep copy. I am using JS for a few years tops, mostly React.

To me its exactly what native languages do with pointers. In some languages (like Delphi) its implicit (like JS) and some (like C) its explicit in syntax.

> Those tend to be employ maybe two cleaners, one depressed robot and one or two jaded administrators, plus their pot dealer.

You just wrote the plot to The New IT Crowd..

Whats the CVE ? [1]

Next Critical Patch Updates by Oracle is scheduled at 15 January 2019. [2]

I see this bug exists at least in part in the open-source parts of VirtualBox. [3] Could it be fixed there?

Could that (that part being opensource) also be reason for the researcher not being granted the bug's bounty?

[1] https://cve.mitre.org/cve/

[2] https://www.oracle.com/technetwork/topics/security/alerts-08...

[3] https://www.virtualbox.org/browser/vbox/trunk/src/VBox/Devic...

Sorry to say but from my perspective you seem to live in a bubble as well, to use your words.

What apps do is add eas of install (app store), and usability (cache, use device sensors, do some offline tasks)

For a webapp the installation is "Add to homescreen" on a webpage. It then behaves like a native app, no address bar. Usability is tackled by modern browsers that allow webapps started like this to: - cache the entire webapp, and some/all data it requests. - run webworkers in background, (get push notifications, etc) - provide sensor access via APIs, (camera, etc) And to conclude, todays webapps respond FAST. They do everything the same way a native app does.

Ofcourse if your webapp does video transcoding or uses some specific OS feature it might profit from being native. But even then, its unbelievable easy to wrap your webapp in a shell that adds these functionality.

How do you think FB and other popular content consuming apps work nowadays? You are basically looking at webapps rendered in a shell that provides the few APIs a browser doesnt yet have, like share button and contact/calendar integration, to get/set data specific to/on your device.

Often overlooked is that not all SAAS are turn-key, where conversion is not a 2-minute endure with a stranger.

For example SAAS meant to complement (relatively expensive) hardware. Conversion is important still, but decided vastly different.

The article shows a screenshot where a heatmap shows how users click on the "Get Started" button a lot and then goes on to state:

Looking at these results, the CTA variation design results are much more focused, with hardly any clicks on other elements. I’m calling this a win.

As if getting people to click this button was the goal. Which is is not, the conversion to an engaged user/customer is.

The alternative there was a email input field plus button, which also received the bulk of the clicks, and immediately resulted in commited users providing vital contact information.

For example, i would click this button to see whats hidden and subsequently leave the site anyway. Many users clicking this button as the heatmap shows are not actually engaged and converted..

I agree, gains should go to reading the code most of the time. But when you say

> It is a suspect proposition that anything is gained by turning 3 lines of code into one line of code.

Some code is way more verbose than its description would be. A named function signals intent:

  function multidimensional_transform(the_data)

And for Javascript ES2015 there is new syntax (like spread operators) that improves code the same way.

Try Unraid on your home server: boots from USB and runs in memory, no raid risks but have network share span several HDDs, parity HDDs, use SSD for cache.

No kubernetes involved - just a webinterface to run containers, install dockers as "apps" on your server. And Unraid is linux, you can but dont need to tinker.

Unraid is how i started using Dockers and became happy friends with my home server again. (tm)