171 karma · joined February 19, 2014
AV1 eliminates MPEG licensing issues, but encoding in hardware is even more limited. Also, AV1 is great for encode-once use cases (e.g. YouTube) since it's heavily geared towards reducing bandwidth requirements vs. encode speed. It's workable for real-time streaming in the lowest settings, but H.264 is still better overall.
While RDP may run okay on 56k with low color mode for some use cases (e.g. simple Windows admin), it requires significantly more bandwidth and compute overhead (either CPU or GPU) for other more advanced use-cases (e.g. video editing, CAD etc.)
So -
* VNC: Low overhead / Low fidelity
* RDP (and other remote desktop protocols, e.g. Frame Remoting Protocol, Horizon Blast, Citrix ICA/HDX): Higher overhead / High fidelity
What is the total overhead (in terms of cores, memory) of the management layer with Oxide (incl. block storage, vmm, etc.)?
If IPO pop was something nefarious, how do you explain IPO pop of Goldman Sachs stock? They ran their own IPO and you can be sure as hell that partners didn't want to leave any money on the table.
In general, IPO pop is an interesting phenomenon and it's not fully explained in the literature.
Referring to him as CEO of a publicly traded company (which he factually is) is quite generous. His hedge fund was apparently a pump and dump scheme (generally hard thing to prove in court, so he got away with it). He eventually lost all of investors' money, which he repaid by allegedly committing securities fraud that he's arrested for. The two companies that he started (fired from the first one for fraud, then started the second as a carbon copy) were simple sham operations where he would use the equity from public investors to buy life saving drugs and then simply jack up the prices to make it NPV positive. No real research, no science, just media hype and b/s.
Hope that his lawyers jack up the rates at least 5,000%, prosecutors do a good job and, provided charges are proven, a sensible judge puts him away for some time in a real prison, not a country club for white-collar criminals. Just think a place like Sing Sing could be an educational, growth experience for a guy who threatens one's family like that. May just show him how tough and smart he really is.
Markets respectfully disagree, see the uptick across all indices since the announcement.
As you point out, there is only so much Fed can do and they are taking a measured, responsible stance, well within expectations. The fact that Fed's actions are fully aligned with expectations is kind of the point - the last thing they want to do is spook the markets, so messaging and signaling is key.
Corporate VCs are effectively a way for cash rich corporations to buy call options on promising and/or potentially disruptive teams and technologies and keep close tabs on what is happening and how things are progressing. I can't think of a situation where corporate VC was a markedly better outcome for a startup or entrepreneur than a traditional financial VC.
Redux looks awesome. I am using react-dnd and hot reloader on my current project and they are great. Thank you for all the great contributions you are making to the ecosystem.
The idea of modeling the store as a reducer is clever. Complication I see is that my action creators are often not pure functions (i.e. there is generally a side effect to update the database and persist the change). However, given the focus of redux on improving the dev workflow, I suppose database updates/side effects could be mocked out. How would you handle this scenario?
What would actually be awesome to have and go hand-in-hand with redux is an immutable write-only isomorphic database (for application state persistence), where you use the same initial state/reducer for redux and the database. Database stores initial state, logs actions and computes the current state using the reducer (and caches it) - much like redux on the client. Curious to hear what people think about this or if anyone has seen anything like it.
The key benefit of React is an extremely low cognitive load. There are only three simple concepts to grok (props, state and lifecycle) to get productive. The code is very easy to reason about (components are essentially pure functions of props and state) and debugging is much simpler than with vanilla JS or jQuery on a project of any meaningful size.
With respect to performance, React shines when it comes to DOM mutations (e.g. removing a div from DOM, creating a new div, inserting new div into the DOM) which is what you generally encounter with the real-world load. Here is a demo illustrating such load [3]. Benchmark offered by OP is amazingly contrived (actually it feels designed to show React in a bad light and lack of full source code is very telling). I struggle to think of a real-world scenario of append-only page with 1000+ images in the DOM, there is simply no valid reason to do that. React in turn makes it really easy and fast to implement infinite scrolling (similar to UITableView) and there are a couple of good open source components that address that.
[1] See the bottom of https://aerotwist.com/
[2] https://aerotwist.com/blog/polymer-for-the-performance-obses...
While there is really no substitute for good coaching, first hand experience, mistakes made and good feedback, here are a few quick tips that I've picked up over the years -
1. The best and most engaging presentations simply have a title that captures the key point and a nice/fun background photo that supports/illustrates the story. Audience will pay attention to the story instead of reading text off the slide.
2. To highlight a fact, keep it to one fact per slide. Make it short and direct (e.g. "3x faster" rather than "212.32% performance improvement").
3. To illustrate a quantitative point, one chart per page is okay, but it must be super simple and easy (absolutely no 3D nonsense, at most 3-4 bars/2 lines/3-4 pie slices, clearly labeled axes). Multiple charts are sometimes okay, but they must be each super simple, belong together, have the same scales and tell a clear and obvious story. Effective charts are a topic of its own, anything by Tufte is a great head start.
4. If you must have more than one point on a slide, keep it at 3 direct, concise bullets per page (if any bullet wraps with a large font, it's too wordy and unclear). No sub-bullets or additional explanations should be necessary. Two bullets is too little (i.e. condense it to one key point), four is too much.
5. No more than one simple diagram per page. Best to keep it to the title that captures they key point and a diagram. Additional explanatory text should not be necessary - if title + diagram can't stand on their own, they are not good enough. Also, if the point of the diagram is not immediately obvious to someone looking at it for the first time, the diagram sucks.
6. Avoid wall of text (e.g. that NASA slide on Columbia's tiles) at all costs. Audience will start reading the slide, completely tune out what you are saying and then get bored half a way through and give up.
7. Contrasting points or showing contradictory data/ideas requires extra care to avoid cognitive dissonance.
8. Background should be as plain as possible. White is best, black/gray could be okay. Anything else pretty much sucks. All text in one color, with great contrast to the background.
9. Timing/length of presentation is super important. Generally, it is very hard for people to stay focused for more than ~7 minutes, so it's good to cover a point in less than 7 minutes and then change it up a bit (e.g. change presenters, show a video, get to a different topic). Overall, presentations should be less than 30 minutes, 45 minutes tops. Anything longer than that is simply too long, you'll lose the audience. Here are two books on the topic I found helpful. They are easy to follow, very short and to the point - "Style: Toward Clarity and Grace" [1] and "Guide to Managerial Communication" [2].
* * *
Overall, the piece feels quite trashy - it dumps all the blame where it doesn't belong (tool vs. lack of presentation/communication skill). Those slides could have very well been made in Keynote or Reveal.JS and they wouldn't suck any less. The piece is also not constructive, it doesn't give reader any hints or tips how to make presentations better.
Finally, a great counterexample to the main point of the piece is pretty much every slide deck that comes with Apple/Steve Jobs' keynote. The best part is that no one remembers or pays particular attention to the deck, but if you analyze the presentation more closely or watch it a couple of times, it becomes clear how effective the decks are.
There may also be some survivorship bias when it comes to the colonies. First colonies often failed and for quite a while (e.g. Roanoke nearly 100 years after Columbus), so I doubt it was all fun and paradise.
Actor model is arguably the most robust with respect to the proposed classification, but the authors also point out that it is not be-all and end-all and that specific problems or even portions of your system may call for different patterns.