http://security.stackexchange.com/questions/16085/how-to-get...
1,371 karma · joined February 3, 2014
http://security.stackexchange.com/questions/16085/how-to-get...
Using "final" also has some performance wins by reducing dynamic dispatch. [1]
Keeping things clean, though: buy a box of 70% isopropyl pads (about 1"x1" squares) at your CVS/Walgreens and use them to clean your keyboard, mouse, door handle, kitchen counter, etc. Works great and leaves no residue. Don't use on wall paint and other alcohol-soluble surfaces.
There is no virtue in being less privileged, and more privileged aren't necessarily morally bankrupt.
Disclaimer: customer for many years
Why these make no sense:
- They take up a good chunk of a page and consume both paper and the reader's time.
- These forms aren't exactly optional, so I am going to spend time filling them out anyway. They would be easier to fill out if they were electronic, and if I wasn't repeating the same entries for the Nth time. The long disclosure adds nothing to usability and is only taunting.
"Paperwork Reduction Act Statement: A federal agency may not conduct or sponsor, and a person is not required to respond to, nor shall a person be subject to a penalty for failure to comply with a collection of information subject to the requirements of the Paperwork Reduction Act unless that collection of information displays a current valid OMB Control Number. The OMB Control Number for this information collection is <number> Public reporting for this collection of information is estimated to be approximately <n> minutes per response, including the time for reviewing instructions, completing and reviewing the collection of information. All responses to this collection of information are mandated by <statute>. Comments concerning the accuracy of this burden and suggestions for reducing the burden should be directed to the <agency> at: <addr>."
That said, it sounds like NYT (a newspaper of record, btw) did more than reasonable selective reporting, to evoke certain feelings in the readers, to get clicks, to start a conversation, or what the reason may be. And it's lousy to see this in modern news reporting. Even the respectable publications err on the side of sensationalism, and it's notoriously hard to get unbiased information as a reader.
Where can someone go to read unbiased, well-researched, both-sides-of-the-story news?
Going further, even the prompt to "delete and then re-download apps due to insufficient space for OS upgrade" seems unnecessary, as if revealing an unimportant implementation detail. Why can't it just automatically do the right thing? I won't mind if the app is missing from my iPhone for a couple of minutes. If the reason is bandwidth, perhaps it could say "we'll do this on wi-fi only."
Similarly, I wish purchased iTunes media started working the "streaming" way, too. I don't want the TV show to take up Gbs of disk space, don't particularly care for the physical file present on my disk. Could still have an opt-in "use offline" option for those who need it.
Or are these all issues to appease people who want to feel like they "own" content (apps, media, etc.)?
What about redefining this word to mean, for some individuals at least, "I'm pursuing my dream"?
Over what I feel like the last couple of decades, we've been taught that work == bad, life == good. You work because you have to, you trade time for money, you suffer from 9 to 5, you anxiously watch the clock, and then you go home and enjoy "life."
I think this is sad. There's nothing wrong at all with productive work, and putting best years of your life into doing something creative like building your life's business.
"The Go devs have since stated that they were surprised to see that a lot of Go converts were from dynamic languages like Python and not C or C++. Go still makes sense for a lot of apps ... somewhere, however, that has been extrapolated to the idea that Go is a good language for writing web apps."
I think this is the crux of the question. And heck, it's very easy to spin up a web server in Go, and so many intro examples focus on that.
Re: web framework. Absolutely, no intention to reinvent the wheel. Just informative to rewrite various pieces in the initial stages to get a better grasp on the language/patterns.
Using "lib/pq" (Postgres) for the db.
Also: need to cache some computed data in memory, and reload using a REPL or other means, haven't figured out the most "batteries included" way to do so yet.
Also: need to figure out the most production-friendly way to redeploy code (sounds like Erlang/Elixir can do really well in this regard.)
I'm an indie developer building such a back-end (social networking/chat space), have full choice of language. Started using Go earlier this year and mostly happy with it.
Should I switch to Elixir in my next iteration? Would it make me more productive, or save me from various deployment hurdles in long-term?
(Please don't take this as one of those mostly aimless "Hey, is Ruby or Python better?" type of questions. I hate those myself. I'm going to be investing thousands of hours into Go at this point. Hoping for some serious pro-vs-con discussion, hoping people who have architected something big in either language could chime in -- such is the major plus of asking on HN.)
I tried Googling, and the best/most recent I found was this thread. [1]
[1] https://www.reddit.com/r/elixir/comments/3c8yfz/how_does_go_...
If he returns to spamming again and again, doesn't it mean that the punishment is lesser than the gains to be had? And too bad.
It may be more work, but if you're not going to build an actual native app, why bother? These apps are built as a sales point ("look, we have a Mac app!"), without the customer in mind.
Same with Slack's Mac app. As beautiful as it is, there's just something that doesn't feel 100% responsive/right with a web-based app.
"With separate code bases for OS X & Windows
converging on a single design, we knew that
sharing code would be essential going forward.
Sophisticated as the graph is, implementing
it twice would have been a significant burden."
How is it ever reasonable to prioritize coding convenience over the end users' experience? This team set out to solve a cool engineering problem (code reuse) and forgot altogether that people are actually going to be using this stuff.FWIW, Fastspring is fairly customizable! The value over Stripe is that you don't have to deal with PCI details or worrying about fraud. Also, taxes/VAT in various jurisdictions. (Disclaimer: current customer)
One minor con is that until your store is "vetted" (something like a few months of successful transactions), your checkout form will include mailing address and phone number fields for additional fraud screening.
It's great to have more options of course. I figure I will "graduate" to Stripe if my operation gets to the point where I want even more control.
2.6 Apps that are "beta", "demo", "trial", or "test" versions will be rejected [1]
[1] https://developer.apple.com/app-store/review/guidelines/mac/* For updates, use Sparkle framework. [1]
* For licensing, use CocoaFob [2] or write your own.
* For payments, use FastSpring like most other indie shops. [3]
Only other detail is having to write a EULA yourself.
[1] http://sparkle-project.org/
It also seems like few users browse there. Being in "Top 100 Paid" takes only 20-30 downloads, which underscores how low the traffic is. Source: personal experience.
What physical innovations actually drive the processor releases, or even flash storage sizes? I understand that each generation shrinks the transistors. But what tangible things were invented in 2015 to make the transistors smaller? Is it that in order to make them smaller, Intel has to run some kind of circuit optimization calculations that weren't possible the year before? Or are there advances in manufacturing (e.g. physical inventions of new molding processes, new chemical processes, something else?) Or is it simply market forces driving the prices and the specs?
(Edit: not meant to be a political statement, more of a practical observation. I only recently started using Go.)
After suffering for years with monthly contacts (dry eyes, discomfort), I'd only wish I'd learned this sooner.