pweissbrod

No im pretty sure in any case i dont want to be eaten :)

I like this analogy.

To take it further I'm equally as fine with me eating an 8-bit animal as I am with a 64-bit being coming into my house and eating 32-bit me :)

Does gitlab have free integrated PR code review tools?

I paint (mostly acrylic) and code. To me, the notion of building a practice run is very liberating; it enables me to think about components, how they should be named/organized, how they interact without the pressure of "getting it right the first time". The time-box for throwaway work should be small. Small enough such that you feel a firm confident grip on the plan at hand. If you have something fully end-to-end operational then more than likely the throwaway has been overworked.

I encourage you to consider trying out more throw-away work before writing the real thing. You find yourself with not only a more lucid vision of what goes in to the "real thing" but a little more muscle memory in getting started down the right path.

Vim also supports org mode as well. Not quite as nice as emacs but it gets the job done for me

"days when you were anonymous, getting to know strangers through common interests and exchanging ideas. I do miss those early days"

That's what HN is to me right now. Yeah it's not truly anonymous but almost everyone here's a stranger to me and I have some wonderful discourse with like-minded perceptive folks any time I visit.

Also reddit to a lesser degree but more experienced redditors than myself this is diminishing I don't fully understand that point

Glad to hear things worked out for your client. The key thing is, YOU had to create an exit strategy just for your client.

If the specifications for the serverless platform were "open" then the client could move their stack to different vendor with insignificant planning/risk.

An analogy would be vendors somehow changing machine virtualization such that your code was required to be very hypervisor-aware to function, and porting from vmware to xen imposed significant cost and risk.

Vendor lock-in is a serious issue. But there is an upside. Say you're building a serverless API. Say you build it using pyhton flask or bottle. You can use a packaging framework such as Zappa such that it can be deployed to serverless hosting or it can run in uwsgi / nginx on a server.

Id be delighted to see a universally adopted standard specification for serverless computing including management interfaces and platform compatibility. The sort of specification that competing Cloud providers could implement thus better empowering consumers like myself. I have faith it will come around eventually all of this is relatively new

"consider"

Thats not healthy. I've convinced my cat to switch to vaping. Now, he only smokes when he drinks. But I'm a realist about this sort of thing.

The way I use it it keeps channels open. But I'll check it once every few months really. Don't feel the need to quit because I'm not addicted

You underestimate the power of lobbying :)

https://www.opensecrets.org/lobby/clientlbs.php?id=D00003356...

Ever watch 'the jetsons'?

Generation or so back in the USA that was the the general over-the-rainbow vision of where technology would take us.

The robots would do the work while people would afford more time to spend on leisure/artistic oriented lifestyles.

The philosophy of the kernel is to work for everyone's need. Its a good question, if these enhancements are of broad benefit and unobtrusive as they seem it's likely better to upstreaming it vs out-of-band patches.

So the author was excited about the concept of function composition? I'm a fan of lisp but I'm not seeing what's particularly novel about lisp here.

This resonates. I once sought to create a DSL on top of F# for workflows only to end up inventing lisp again. It was a humbling experience. The thing about lisp and why I dont use it in the workplace regularly is that it's dense and inconsistent. Dense because it's easy to write a profound amount of logic in one line which hurts readability if youre not careful. Inconsistent because you and I could be master programmers and write perfectly effective solutions that do the same thing and the code can look entirely different. This hurts interchangeability and it doesnt scale well, which disqualifies it from most enterprise projects. Similar to perl. That being said all my personal projects are done using clojure because it's such an easy/fun platform to work with

I'll take the "volkswagon special" for one please

I'm no prison security specialist but right in downtown Manhattan, of all places, sounds like the least secure spot to host this powerful escape artist of a drug lord of anywhere in the country.

Explosive user growth in "free" SAAS and social media starts to taper towards a limit.

Public companies, pressured to maintain that revenue trajectory, compensate reduced growth by squeezing more value from existing users.

This tends to lead towards more obtrusive advertisement, aggressive data collection which, if not carefully implemented, leads to negative publicity and attrition.

The struggle in 2018+ is to find what we collectively considers "acceptable privacy", or in other words where is that line between what valuable personal information folks will offer up and what's considered generally creepy.

welcome to the nosql of 2018

I mildly disagree in the sense that what constitutes a "palpable" error is just too broad of a grey area.

It would be encouraging to see FanDuel just cough up the erroneous wager (which is surely cheaper than a lawsuit) and tighten down the definition of errors in spreads to something more specific such as anything outside like 2 standard deviations within the scope of a game*

*I'm not a gambler just someone who believes the definition of error can be mathematically defined for everyone's benefit

I havent been following this closely but the notion of "speedy shutdown of content by the ISP" sounds strikingly similar to the late [SOPA bill](https://en.wikipedia.org/wiki/Stop_Online_Piracy_Act) in the US (2011). Is this effectively similar to SOPA?

I'd be interested in knowing more about how this particular connection was made. Do you have any educated theories on how the message was inferred?

I spent two weeks trying out the evil mode in my daily workflow. Some things were much more user-friendly than vim but at many points the rough edges of the vim emulation on top of emacs showed its bare spots. Finally, lack of support for a good database client bought me back to spacevim which is a similar space-driven IDE written in native vim.

I wonder if there exists a parallel dimension where linux is microkernel design and folks are pushing for monolothic citing the driver friendliness and performance

If your statement is correct then a workaround would be to perform scraping in a non-covered country such as CA and, once extracted, proprietary barriers are thus removed returning ownership to the individual.

My guess is that America in 2018 is more selfish and cliquey than any other time in memorable history. That simple really

Totally agree with this. When was the last time you were in line at a coffee shop? Everybody staring into their phones. Compare that with sometime from like the early 90s where conversations would start up between folks inline. All these people staring at their phones it looks like the eighties equivalent of a Twilight Zone episode

When powershell 1.0 came out I LOVED the concept of piping objects like so much streams. In my experience there were two camps of powershellers, the scripters and the programmers.

The scripters, probably the more experienced folks would use abbreviations, shorthand and all-lowercase. The programmers like myself would predominantly use powershell on less-frequent occasions to glue our apps together and PascalCase and verbosity has already been burnt into our brains.

Powershell, like perl, took that philosophy that welcomed both parties to write code as they pleased.

But then powershells 2 and 3 and 4 came out, and all that stuff I learned in v1 became deprecated. And I wanted a powershell script that would just reliably run on any, say, windows machine 2003 or beyond. But when I google for something like 'how do I invoke an osql.exe query command? how to escape the quotes?', or, 'how to load a dll and having an adjacent config file and run a method?' I get so many different answers ranging from woefully misguided to version-specific to syntax so wildly different to the untrained eye they look completely different yet being effectively equivalent. I inevitably spend hours crawling google and cobbling together the bits that work cross-platform, document heavily and sit in amazement at how much work it took to do something one would think was simple.

It's a shame but my experiences with powershell as an occasional user have shifted from enthusiasm to seeing it as an arcance even punishing experience when I'm used to bash or python.

I hope this doesnt sound mean in any way, its just that when youre talking with a computer, words like grep/sed/awk and regular expressions bear a learning curve but once you get past that barrier it is much easier to communicate succinctly with the computer with what you really want to do.

There's a significant cost covered by the inventor as they carry the burden of trial and error which comes with developing something novel/pioneering.

Now, in the bigger picture, I agree with you that sharing knowledge and innovation benefits the greater good over longer term.

But the thing is, if you copy these novel inventions in secret, close up access to anyone else being able to benefit and establish trade embargoes then its more like stealing than copying.

It's sort of like if Aaron Schwartz sold books to private buyers instead of open sourcing them.