Even so, I often store images within my online notes. Linking out to them is one option, but of course means that my notes would be dependent upon a third party host. Being able to paste image blobs into the document and store them with the text would be an advantage if I were to want to use this.
That makes sense. Do you know why they aren't more common, to the extent that many doctors apparently spend much of their day on EHR data entry?
Maybe I'm just relying too much on this article plus a few similar complaints I've read in the past. Maybe most doctors don't spend much time on data entry but I only see the grievances of the few that are forced to.
XAML is a template, JSX is a DSL. A template kills scope, duplicates coding semantics, messes up app flow with bindings and needs dependency injection to get local scope back - all of this has been solved with JSX, which now pretty much fulfills Silverlights dream: https://news.ycombinator.com/item?id=16198843
The crazy part is, that you can share code and eco-system components among these targets, no matter if they're native or otherwise. Here's a shell applications for instance that uses react-motion to shift stuff around: https://github.com/gaearon/react-blessed-hot-motion
Microsoft seems heavily invested in it as well (react-windows, reactXP, UI-fabric, ...).
XAML components ("controls" in MS terminology) contain both declarative markup and code. And it's flexible because the visual presentation can be completely overriden by the component's consumer without altering behavior, and your code can be either C# or C++.
What does dependency injection have to do with anything? There's nothing stopping you from using global variables or an event bus or something like Redux in a XAML app.
I’ll put in a plug for my former employer’s OpenLaszlo, introduced in 2002 (preview) and 2003 (version 1.0).
OpenLaszlo was most immediately inspired by HTML and (for data binding) XSLT. I looked at Mozart for ideas on constraints, but we ended up rolling our own design — mostly because constraints were never supposed to be a feature, so they were designed and developed incrementally, in discretely releasable baby steps.
Adobe did due diligence of the company sometime around 2002-2003 too, but that deal fell through. An Adobe PM also signed up for our beta program, initially under a pseudonym, but he eventually came clean. I’ve always been curious whether Flex/MXML was related to either of those encounters.
Adam Wolff, former Chief Software Architect of Open Lazlo, is now the Director of Product Infrastructure at Facebook, and oversees React and React Native.
Adam developed the initial runtime implementation of data binding and constraints — with additional help from Max Carlson, and, later, P. Tucker Withington and Henry Minsky — while I did the compiler work and language design[1][2]. Adam et al wrote the runtime constraint resolution mechanism, which initially had an API for the procedural creation of constraint graphs. I was trying to make constraints and data binding look like JavaScript expressions, that were automagically recomputed when a subexpression value changed, by extracting dependency graphs from the source and packaging them for runtime use. (All this on the Flash 5 bytecode interpreter, which was slow as the dickens, even for the time — so there was a lot of optimization: in the compiler, in the runtime, and in the interstices. Although nothing like we did later for [3].)
This was the bottom of a slippery slope, where the designers and developers using the platform were exploring the kinds of applications it was possible to write (single-page web applications were relatively new in the early oughts — except for some pioneering Explorer-only DHTML work by Microsoft, which we should have looked at but didn’t — and we were all making up interaction patterns and software design idioms as we went along), and we were adding the platform features to enable some capabilities and golf others.
For a while Adam ran Laszlo’s Professional Services. He succeeded me as CSA when I left Laszlo.
It wasn’t Flex/MXML or XAML that killed Laszlo/OpenLaszlo, it was IMO first-gen dynamic frameworks such as Prototype and Scriptaculous, that could be gradually integrated into a page without placing a big rewrite-your-app bet. Also that we were about a year late in adding HTML as a second back end. (HTML wasn’t sufficiently standardized or practical to use for cross-browser single-page applications in 2001 when we started work on the Laszlo platform implementation, but it was by 2005-6.) Or, closer to the root cause: sales and strategy issues that made it difficult to keep investing much in the platform once it was starting to get traction; the product feature omissions are how those resource constraints played out.
I don't think what Windows provides is really comparable. By my understanding (and the documentation you linked seems to back this up) WDM is responsible for taking 2D framebuffers from applications, and compositing them into a (possibly 3D) scene. Fuchsia's Scenic operates uses a 3D scene graph as its input.
About the same here in Seattle. It makes saving for a down payment even more depressing.
I don't understand who is able to buy these houses when my partner and I can't as software engineer + physician assistant. Maybe it's just because we're not willing to decrease or dip into our retirement savings and we have no help from parents.
I just don't feel comfortable taking out a jumbo mortgage. Even though we could make the numbers work, I'm not confident either of us won't burn out from our stressful careers.
I live in Portland but I’m in the same boat you are. My wife and I make a decent amount of money ($120k+) but a combination of student debt, crazy housing prices, and lack of wealthy family members who can “gift” a down payment leaves me fairly hopeless that we’ll ever be able to buy a house of our own.
We’ve seriously considered moving to the Midwest or the South where houses are affordable, but neither of our jobs allow fully remote work, very few cities in those areas have any sort of tech presence, and we’d be leaving pretty much every family member across the country.
I live in the area as well and I think the reality is that Seattle is going through a massive change due to densification.
Nobody expects to be able to buy a single family house in NYC- and that will probably soon be the case for cities like Seattle and SF...however this is a relatively recent development for us and therefor a much harder pill to swallow.
I came from the midwest (born and raised) - to respond to the other commenter...home ownership is cool, but I like it out here a lot more. Also, I make WAY more money here. Like 50% more, and I'm at the bottom of the engineer food chain. I make more money than any of my more experienced senior engineer friends back in the midwest. The amount of outdoorsy opportunities, interesting companies to work for, and boom/bust culture is just too exciting. Midwestern cities also experience a lot more violent crime (check out any top 10 list of dangerous cities). I think I heard gunshots almost every night that I lived in Kansas City, MO.
>Despite the acres of news pages dedicated to the narrative that millennials refuse to grow up, there are twice as many young people like Tyrone—living on their own and earning less than $30,000 per year—as there are millennials living with their parents. The crisis of our generation cannot be separated from the crisis of affordable housing.
>More people are renting homes than at any time since the late 1960s. But in the 40 years leading up to the recession, rents increased at more than twice the rate of incomes. Between 2001 and 2014, the number of “severely burdened” renters—households spending over half their incomes on rent—grew by more than 50 percent. Rather unsurprisingly, as housing prices have exploded, the number of 30- to 34-year-olds who own homes has plummeted.
>Falling homeownership rates, on their own, aren’t necessarily a catastrophe. But our country has contrived an entire “Game of Life” sequence that hinges on being able to buy a home. You rent for a while to save up for a down payment, then you buy a starter home with your partner, then you move into a larger place and raise a family. Once you pay off the mortgage, your house is either an asset to sell or a cheap place to live in retirement. Fin.
>This worked well when rents were low enough to save and homes were cheap enough to buy.
...
>Since the Great Recession, the “good” jobs—secure, non-temp, decent salary—have concentrated in cities like never before. America’s 100 largest metros have added 6 million jobs since the downturn. Rural areas, meanwhile, still have fewer jobs than they did in 2007. For young people trying to find work, moving to a major city is not an indulgence. It is a virtual necessity.
>But the soaring rents in big cities are now canceling out the higher wages. Back in 1970, according to a Harvard study, an unskilled worker who moved from a low-income state to a high-income state kept 79 percent of his increased wages after he paid for housing. A worker who made the same move in 2010 kept just 36 percent. For the first time in U.S. history, says Daniel Shoag, one of the study’s co-authors, it no longer makes sense for an unskilled worker in Utah to head for New York in the hope of building a better life.
>This leaves young people, especially those without a college degree, with an impossible choice. They can move to a city where there are good jobs but insane rents. Or they can move somewhere with low rents but few jobs that pay above the minimum wage.
>This dilemma is feeding the inequality-generating woodchipper the U.S. economy has become. Rather than offering Americans a way to build wealth, cities are becoming concentrations of people who already have it. In the country’s 10 largest metros, residents earning more than $150,000 per year now outnumber those earning less than $30,000 per year.
We're on a small rock flying through an infinite universe. Our lives exist in a small blink of time. Computers run billions of operations per second using software with countless defects at every level of the stack.
We're lucky anything works at all. In that context, we succeeded just by being born and living as long as we have, and we'd be pretty narrow-minded to assume that the material success we enjoy is significantly more than a series of happy accidents.
Not sure why you're being downvoted. XAML definitely supports complex widget composition in markup. Since the XML is basically just describing an object graph, it's a more concise way of writing the equivalent imperative code:
One cost of all the guns is all the extra security. Schools resembling prisons, TSA, metal detectors and surveillance everywhere... doesn’t that also infringe on my freedom in a way?
Is that a cost of the guns, or the 'war on terror' stuff that became an obsession after 9/11? Because it's not much better in many places outside the US either.
http://www.gutenberg.org/ebooks/1342
:)