I've tend to chat with drivers when I take Lyft, and frequently mention that I'm a programmer. Several of the drivers have then asked me about cryptocurrency, mostly Bitcoin and Ethereum. I try to discuss how technically interesting they are, but how financially shaky; that there is likely a bubble and that they are probably not good long term investment options but could be worth buying a little bit for fun.
We are definitely in a very hype driven cryptocurrency bubble right now, and there are a lot of naive folks who are probably going to lose money to it.
And yet somehow, we haven't really managed to make any cryptocurrencies an actual, widely accepted, payment alternative, for anyone other than a few people with special circumstances (government restrictions on currency exchange, criminals demanding ransoms, funding organizations that governments are trying to shut down) or people who are fairly technically competent.
There's a chance the lightning network could be the last piece of the puzzle to make cryptocurrencies actually usable for payment, though even still, I have a hard time seeing most places wanting to accept payment in an asset as volatile as Bitcoin.
Or maybe we'll see a coin backed by fiat currency and real, regulated banks on Stellar, where you don't have nearly the same scalability issues nor gigawatts of power wasted just to try to solve Sybil attacks. If you have a coin backed by fiat currency, and low transaction costs, businesses are a lot more likely to accept it as payment as most of their expenses, taxes, debts, and so on are in the local fiat currency rather than than in any cryptocurrency.
That too. The deflationary nature of Bitcoin makes it really unsuitable for use as an actual currency, and of course the amount of speculation going on.
Everyone I know who got into crypto has the same story: for some silly reason they all bought like 5-10 different coins and it would be inordinately complicated and expensive to sell them all.
I'm pretty sure whatever "newbie guides" exist out there purposely lead people to this awful state.
"Crypto" is short for "cryptography" (or related words like "cryptographic").
Using "crypto" to abbreviate "cryptocurrency" causes a lot of confusion, as the "crypto" in "cryptocurrency" was already an abbreviation; "cryptocurrency" is short for "cryptographic currency."
People who know nothing about cryptography or even that cryptocurrency uses cryptography get confused if they are looking for information about cryptocurrencies and instead find more general purpose resources on cryptography (like https://crypto.stackexchange.com/ or https://www.reddit.com/r/crypto/).
I know that this is a losing battle, like getting people to stop using "wiki" as an abbreviation for Wikipedia (which is just one out of many wikis), but I figure that as long as we're talking about people not knowing much but investing in it anyhow, I really encourage everyone to stop using "crypto" as an abbreviation for "cryptocurrency."
> "Crypto" is short for "cryptography" (or related words like "cryptographic").
You know who decided that? The population that was using these terms.
Now a similar population at large has decided the new usage rules. It's normal, it's just evolution of the English language. By this point, "crypto" is indeed widely used as a short term for Cryptocurrencies also.
People who know nothing about things are going to get confused either way. The society can't form every single rule just so every person who doesn't know anything will have a clear mind. If they want to learn something, they will. And learning that "crypto" can mean two things, in a language where it's already commonplace for terms to mean different things in different areas - is not a huge thing.
> Now a similar population at large has decided the new usage rules. It's normal, it's just evolution of the English language. By this point, "crypto" is indeed widely used as a short term for Cryptocurrencies also.
Yes, this is why I say that I know this is a losing battle.
I mostly care about it in the context of technical forums like Hacker News. While the word may have a different meaning for the population at large, when you're having a discussion on a technical forum you should generally try to learn how words are used in that context.
This is somewhat like the different meanings for the word "theory" in a scientific context and in general use. In general use, "theory" means an idea that may not yet have been tested or proven, somewhere around the meaning of "idea", "hunch", or "hypothesis", while in a scientific context "theory" indicates something that has been tested successfully and is well accepted.
While the use of "theory" in the broader sense is well accepted in general use, using it in that sense in a discussion about scientific theories is confusing; so if someone does that in such a discussion, I am likely to point out the stronger meaning of the word in scientific usage.
So likewise, while "crypto" as an abbreviation of "cryptocurrency" is already fairly widespread (though I think still niche enough that there's a tiny chance a concerted effort could change usage patterns), I at least want to make sure that folks getting involved in technical discussions are made aware of the earlier definition of "crypto" and are made aware of the confusion that can be caused.
It's a true open standard developed collaboratively by multiple competing top-tier companies, has multiple interoperable implementations, has been designed from the ground up for running untrusted code in a sandboxed environment, has been designed to be a general-purpose compilation target rather than with tight coupling to a specific source language, it has enough killer apps that is will likely continue to be developed and supported by these multiple companies, and it was developed with the hindsight of many of these previous failed or only partially successful efforts.
Some of these previous efforts might have one or two of these features, but none of them meet all of these criteria.
It has the bubbles around what each person says, which is the style that many of the chat apps in your link have as well.
OK, they are flat bubbles now rather than shiny blobby ones, but it's the "bubble for everything someone says" that makes it look dated.
I hated the "bubbles" look back then and always used themes that just presented text as text, with possible unobtrusive delimiters between people's comments. Like Slack and Discord do.
There are two reasons you might want to share the link to an HN discussion: if there is interesting discussion going on, or if you want to encourage people to upvote it.
In this case, there is no discussion about the article, just about the upvote brigade. So the only reason for sharing the link to the HN discussion would be to get people to upvote it.
As a "little guy" who lost a lot of USD and Bitcoin in the MtGox fiasco (luckily, nothing I couldn't afford to lose, though with the price BTC is trading at now it would be really nice to still have those BTC), and any possible partial payout through the bankruptcy process is tied up in potential litigation, I'm a fan of more heavily regulated exchanges that I can actually trust.
Since the MtGox fiasco, I've never bothered trying to liquidate any more of my Bitcoin, and instead just occasionally use it to pay for things which accept direct Bitcoin payment.
I'd be a lot happier with a trustworthy, audited exchange.
If there are smaller exchanges that couldn't deal with the regulation, they probably also can't deal with security, keeping enough secure reserves to be able to pay out in the case of losses, auditing both their security and finances to ensure that they stay healthy and liquidate gracefully if they ever run into financial trouble.
Is having the UI layout and styling mixed in with the code considered a feature of Flutter, or is providing a way to specify them separately in a machine-readable or declaritive format just not done yet?
I'm a fuddy-duddy still doing UI in GTK and Qt, I haven't kept up in trends in web and mobile design, but I know that when our developers do the layout and design it comes out awful and unusable, but luckily with GTK and Qt we can just hand it off to our designer after the basic functionality is in place and he can do some layout tweaking with Glade or Qt Designer, and is comfortable with working with CSS to provide us with custom widget styling and images, and then he sends it back to us and we clean up the results and merge it.
All of the Flutter examples seem to have the UI written entirely in code, both layout and styling, and I don't think he'd be comfortable with that. You may note that we send it to him, he tweaks it, and sends it back to us to merge; we've never been able to teach him Git, but that's OK, because we don't expect him to teach us Photoshop and design.
So, I'm just wondering if Flutter is intended to always be like this, with the whole UI specified in executable code that needs to be compiled and run for each iteration, or if it is intended to add a way to separate out the design parts (layout and styling) in a way that they can be worked on at least somewhat independently of the code?
I know that there is IDE support for hot reload, which may be OK for a designer to work with, but I'm always a little skeptical of that since most developers I know use VIM or Emacs and not IDEs, so sometimes IDE tooling setup can break, and once a project gets complicated, the toolchain setup for running from within an IDE can get hard to install. The nice thing about Glade or Qt Designer is that they can work with purely declarative formats so that you don't need to worry about having to have your designer get the full toolchain installed.
Flutter is about simplicity so I doubt they are planning any designer tools.
And IMO, designers should stick to their favorite tool, and leave implementation details to programmers. Hot reload makes it easy (and IDE is not required for that).
> And IMO, designers should stick to their favorite tool, and leave implementation details to programmers.
I'm curious about how this would work if the designers have to use developer tools to do the final spit-and-polish.
I don't know about how other places do it, but what I'm familiar with is that a UI mockup is sketched out and requirements given to the developer, the developer implements something but in the process finds issues with the design as specified and iterates a bit while doing so, and eventually you have something that is functional but somewhat ugly because the original sketch was not specific enough or didn't anticipate some issues that came up or the like, and then finally you give it back to the designer to do the spit-and-polish.
In some cases, the spit-and-polish can be a lot of work, because you've used some new widgets that you don't already have standard styles and graphics for, or maybe it's your first app with a new toolkit and so you need to figure out how to get your branding and style to work with it.
For designers I've worked with, CSS is their favorite tool for styling, and they prefer UI tools for spit-and-polish layout tweaks. Are you saying that they should just deal with having to learn how to do all of that embedded in code, or that they should just hand off their assets and suggestions to the developers and the developers have to do the final spit-and-polish work?
Really makes me cringe to read some of that text, but that was high school.
Oh, and even more eye-bleeding is the page I ran for a Nomic that I was in, and webmaster (sorry, "Secretarylet of the Revolution in charge of Web Pages") for: http://www.nomic.net/deadgames/macronomic/. I don't know what I was thinking when picking that particular shade of red; red made sense, but I'm sure that even with the palettes available back then, I could have picked one a bit less painful.
> these days imagining running linux in 4MB makes me sniggers.
Did you read the article?
> Here it is! Not exactly our target of 512KB of RAM but 768KB is getting pretty close. Some microcontrollers already have more than that amount of available on-chip SRAM.
768 KB of RAM, plus a MB or two for the text sections which are in flash, is not bad. Not quite at the target, a system with 512 KB of ram and 2 MB of flash, but it's close.
I think it's fairly clear that they mean "the birth rate for people in the 20-35 age range, which happens to coincide with the millenials at the moment."
It's pretty clear what they meant, but humorously even your rewording isn't accurate.
A named generation is static, based on the birth dates. The "20-35 age range" is dynamic, anchored to the present time.
Also, named generations (like "Millennials", "Gen Y", "Gen X", "Baby Boomers", etc) don't have rigid definitions. Some media groups define it as starting as early as 1976 and others as late as 1984, which is 50% of your "20-35" range.
In the end, the boundaries of named generations are more or less arbitrary unless there is an extremely specific event which defines it (Baby Boomers started with an explosion of birth rates immediately after the end of WW2).
> A named generation is static, based on the birth dates. The "20-35 age range" is dynamic, anchored to the present time.
Yes, that's why my phrasing used "at this moment." At this moment, millenials are around an age range of 20-35 years old, give or take a bit depending on the very fact that you point out, there aren't well defined boundaries and the exact age range could vary. I was very careful to include "at this moment" in my phrasing, for the reason that you point out. I didn't bother to hedge about the unclear boundaries of the millenial generation, since that wasn't the topic at hand, but yes, these terms are somewhat vague.
The actual article cited simply discussed the nationwide birthrate at different points in time; it didn't talk about particular generations.
Given that millenials are currently the generation that are of prime child-bearing age, it's pretty clear what the original poster meant "people of child bearing age right now, who happen to be millenials, are having less children than those of child bearing age at any point since the great depression."
The original phrasing was humorously incorrect, I just thought that asking for clarification was a bit much, since it was pretty clear what they meant to say, it was just a funny mistaken phrasing.
> I'd say that the amount of knowledge and effort required to get to such a level of optimization is similar to optimizing Javascript.
Really? After reading all of the articles in this series (the original about porting to Rust, the rebuttal about optimizing JavaScript, and this one)?
I'm more familiar with Rust than JavaScript, but I found that other than the algorithmic optimization, the rest of the JavaScript optimizations were very non-obvious in order to achieve an effect that is entirely natural in Rust.
There's no need to be careful to avoid particular types of function calls, since there are no dynamic variadic function calls in Rust. There's no need to resort to using the equivalent of `eval` for monomorphization, it's a natural feature of the language. There's no need to do manual memory management by encoding values into typed arrays of integers; you can simply allocate vectors of structs, borrow references, and so on.
These are all things that had significant cost in JS, and needed to be worked around via some intensive profiling and knowledge of how JIT engines work, but just doing things naturally in Rust leads to a pretty much zero-cost solution.
It's true that if you want to really get into the nitty-gritty of micro-optimization in Rust, you need to learn some more and do things like profiling and inspecting the generated code to see what optimizations the compiler was able to apply or not.
But the Rust rewrite of source maps did none of that; they just rewrote it in fairly idiomatic Rust, and achieved a similar speedup to what a JIT engineer armed with a profiler, a deep knowledge of what affects how well a JIT works, and a willingness to do manual memory management in typed arrays was able to do.
> Having worked/interacted with a lot of people working with Rust on different experience levels, most of them (that includes me) don't have a deep knowledge of what Rust concept maps to a specific concept with which performance implications
What parts of Rust do you feel like you don't understand the performance implications of? I feel like the mental model for performance is relatively similar to C or C++, with relatively few things that would surprise you if you're familiar with modern C++ (in fact, a lot fewer performance surprises than modern C++ offers, in addition to the extra safety).
We are definitely in a very hype driven cryptocurrency bubble right now, and there are a lot of naive folks who are probably going to lose money to it.
And yet somehow, we haven't really managed to make any cryptocurrencies an actual, widely accepted, payment alternative, for anyone other than a few people with special circumstances (government restrictions on currency exchange, criminals demanding ransoms, funding organizations that governments are trying to shut down) or people who are fairly technically competent.
There's a chance the lightning network could be the last piece of the puzzle to make cryptocurrencies actually usable for payment, though even still, I have a hard time seeing most places wanting to accept payment in an asset as volatile as Bitcoin.
Or maybe we'll see a coin backed by fiat currency and real, regulated banks on Stellar, where you don't have nearly the same scalability issues nor gigawatts of power wasted just to try to solve Sybil attacks. If you have a coin backed by fiat currency, and low transaction costs, businesses are a lot more likely to accept it as payment as most of their expenses, taxes, debts, and so on are in the local fiat currency rather than than in any cryptocurrency.