skysight-inc/HackerNews huggingface dataset:
There is definitely a learning curve. For me, Rails was unapproachable until I started to give up the idea that I needed a ton of custom stuff in my stack. The "allure" I saw of pulling together a basic routing system and hooking things up by hand completely disappeared after building a pretty substantial web app in _Sinatra_.

Rails makes a lot of decisions for you, but the decisions it makes are the _right_ ones. It's like having a "best practices" box that you can just shove your custom system into, rather than trying to build them in yourself. It's really quite something.

For context: I basically learned Rails by way of building a proof of concept election management system in Rails in about three weeks (more like 1.5 in actual programming time). It also stored votes on a blockchain (ethereum). Even with a relatively complex storage system and interaction model, the Rails best practices left me with a really satisfactory application in no time flat. Perfect for a fast PoC.
If you need to build an API quickly we just launched https://code.xyz on Thursday. No server provisioning, no routing, nada, just write a JavaScript function, hit deploy, and you have a scalable "serverless" backend. You can deliver any type of content. (We have command line tools available as well, if the web environment doesn't suit all your needs.)

Our company is called StdLib, we're focused on making API development, deployment and management effortless - we're backed by both Slack and Stripe [1].

[1] https://stdlib.com/blog/stripe-code-xyz/
Poor individuals are less likely to get married or have any kids.
You refer to a very qualified and narrow "identical". In the general sense, before an Uighur commits a crime, are they treated in an equal manner to a Han Chinese before they commit a crime? In all manners of expression, association, travel and employment, for example?
In my experience this is vastly overstated.

Also, just because you use Heroku for your app servers (dynos) doesn't mean you have to use it for everything.
If backend speed/scale is your concern I'd also throw a vote in for Phoenix. Lots of similar heritage to Rails but built on Elixir/Erlang instead.
> especially given about half will end in divorce

That ancient statistic is very misleading. It is derived from dividing the number of divorces by the number of marriages. A more interesting statistic is the number of people who get married and then divorced compared to the overall population. This is much lower since some people have a lot of divorces.
J is Readable
Three second setup of PHP sites with atomic updates and automatic DB migrations:

Pre-built LXD image with MariaDB, nginx and PHP. Git for deployment.

Provisioned and live in three seconds with support for rollbacks, migrations, atomic updates and zero downtime.

Should work well for most other scripting languages too.
I just make a spring boot seed application and use it whenever I start new projects.
We do, but it's still at a very early stage :-)
To what benefit, could you share?
Coming from nodejs, phoenix is incredible. Out of the box, phoenix just uses nodejs to generate all your frontend assets, and channels are incredibly easy to use. I'm still learning about how elixir works under the covers, but so far I'm really impressed.
Describing it as a simple loss of $3 million is definitely a simplification, for the reason you mention. But saying this is "very misleading" is perhaps even more of an oversimplification. Unless you are so cynical that you think the normal tax rates are a complete sham -- i.e. that the official tax rates have no basis in reality, such that there is no impact whether a city charges $5M or $0.

But if we assume that that $5M is somewhat tied to the actual costs to the city to administer services and regulation, then offering a $3M tax break is done with understanding the potential opportunity cost, and believing that Amazon's business will more than make up for that $3M that the city might have reaped otherwise.

The point of these stories is that, in the past, there was basically no easy way for the public to evaluate these tax breaks. A situation like Amazon seems like a sure net win. But there are many, many more American jurisdictions than the city that happens to get Amazon's business.
Positivism was actually debunked by mathematics, not philosophy. In fact, this is why Platonism is accepted in mathematics and formalism scoffed at.

Take a look at Godel's incompleteness theorems - they hold that it's impossible to provide a proof for everything (formalization of "this statement is not provable", which is arguably both true and not true, results in a proof that the statement is true but not provably so).

A system containing first-order arithmetic cannot be both consistent and complete because it cannot prove its own correctness itself, as it will result in the paradox mentioned above - it must resort to a higher-order system to do so (metamathematics). Thus, one can never have a firm axiomatic system from which to deduce all non-empirically-derivable aspects of reality, and as a result, logical positivism doesn't work.
This is my go-to as well, incredibly easy and fast to get going but also scales reasonably well.

The only caveat I’d say is I prefer Roda over Rails for APIs and simple projects.
Many of the fruits of positivism are accepted by scientists and engineers, but I think Maudlin is correct in saying that the analytic school has (rightfully) shied away from the central positivist claim (i.e., that "any two observably equivalent theories are one and the same theory"/"a theory says no more than its observable consequences"). We've carried Popper and a few other positivists into the 21st century, but in a form that most would probably be unhappy with.

I agree about the wave/particle description, though. I've read Maudlin before in the context of the philosophy of time, and he is frequently critiqued in that domain for giving inadequate consideration to quantum-theoretic discoveries.
Almost every worker/contributor in the movie/TV industry in North America is represented by a union/guild or is trying to get into one, there are non union projects/studios but those are in the minority.
"Show me the"?
I don't do anything special for prototyping, I just use what I normally do if I were creating the real thing.

> django-admin startproject
> copy+paste my webpack config for React
> copy+paste my general management scripts into the package.json (mostly scripts to build the client, and if working locally also start a server)

Then if I want to deploy it, I just install nginx and gunicorn and again copy+paste my configs for those.

If I want to use mysql it's not too much trouble, takes 10 mins to get it up and running and my application hooked up to it.
It looks more like Tech took the wrong message out of the cartoons.
Please one element of evidence that scrum predates agile.
A loss.
GitLab has been a pain for me lately.

Chose them for a client due to built-in CI (as opposed to Github), but the HTTP response time on the web UI makes it painful to use - I'm routinely seeing ~1s response times on pull requests and CI pipelines, not to mention that the provided CI "runners" seem overloaded and your jobs often stay in a pending stage for several minutes (can be solved by running your own instance of gitlab-runner on an AWS box).

Personally I'm moving that project to Bitbucket - they now have CI pipelines too.
> Government massively subsidizes the oil industry all the time.

Not true. Even if it were true most of the oil industry is losing money hand over fist.

But not as fast as the phony baloney "renewable" industry is, even with its insane subsidies.

People can't wrap their heads around the fact that sane estimates of the energy supply of the future do not support cars. People will be walking and biking and riding buses. The future is a place with far fewer cars.
Like I said in reply to another comment, the marginal increase to the cost of administration is probably a good deal lower than the resulting average cost.
A long career is certainly possible, however, you will earn far less over that career, and see more stress than doing something less exciting. I still miss working on games, playing my own creation with music, graphics, game logic all coming together is the most rewarding thing I've done. Meanwhile, writing code which is judged by output in a console is much more boring, but much more rewarding in other ways. It certainly doesn't make you look at the clock, though, as there are interesting problems to solve everywhere.
it's not far in spirit, but it's still quite far away
Yes, in my time seven years old children could go off on the streets to play for hours by themselves, ride a bike or skate without a helmet, etc. Things have gone in not a precisely healthy direction, in my opinion.
Thanks, though they seem to be US-only, from quick research. Also LoRaWAN does not require a license and can handle lower-power applications with the same network. I will check it out in detail later.
Good Thing™, or just a good thing?
That's unavoidable. He's called manager for a reason. I would replace powerpoint for excel in my experience. Everyone wants a leader they can look up to and admire, not a PM.
> Do you mean damages could not possibly have been enough to pay back your legal fees

Unfortunately yes. The infringer was not big enough to be worth it. However, that meant the patent was then worthless. If you don't enforce a patent you lose it.

Patents only seem to be worth it for large companies and trolls.

P.S. I have always been fascinated by a contrary story. The guy that invented the intermittent window wiper got a patent and the car companies ignored him for a very long time. He sued over and over with no lawyers and eventually got a huge sum of money. Unfortunately he was quite old by then.
37 Signals is well loved.

A lot of people would say Google these days... now that they're starting to move beyond Material Design 1.0 a lot of their products are becoming more visually mature and unique, along with their substantial investment in machine learning to make their software more personalized, etc.
Have you guys applied these more technical/scientific details of the brain to your life?
I tried both Flutter and ReactNative. I am not an expert, so take it with a grain of salt, but here is my first impression:

I would say the best part about it is the hot reload, which maintains application state. It's compiled to native code so it's going to run faster than ReactNative which is a javascript bundle that runs besides your app. Compile times are fast, but not instantaneous and you have to trigger the reload manually.

I think it also has the most complete implementation of Material UI out there. It implements widgets that are not implemented in iOS, Android nor Web. It's like having something like bootstrap that makes it easier to build a good looking app. I feel like you really need a mock first to build a reactnative app, but you could get away with just writing code in flutter.

Unlike ReactNative there is no way of trying it without installing the Android or iOS development environment. Initially that was a bit of a barrier for me as a first-time mobile dev, but not a big deal eventually.

It's not as mature as ReactNative. There was no build-in way to do audio, something I need for the app I am trying to build. However, I found a plugin for it on github.

I know Google has a reputation of canceling projects, but Flutter is used to develop the Google AdWords app so I don't think it will go away anytime soon.
> It's just not sustainable or healthy to be working 60+ hour weeks and not taking any vacation

This seems to be a huge problem in many fields. I know it's a problem in medicine, and regulation of work hours doesn't appear to be particularly effective. This 2006 article compares the workload of medical students (who are paying to work in order to learn and gain experience) before and one year after work hours regulation:

https://jamanetwork.com/journals/jama/fullarticle/203251

> Working shifts greater than 30 consecutive hours was reported by 67.4% (95% CI, 64.8%-70.0%)

> Averaged over 4 weeks, 43.0% (95% CI, 40.3%-45.7%) reported working more than 80 hours weekly

> 43.7% (95% CI, 41.0%-46.5%) reported not having 1 day in 7 off work duties

> 29.0% (95% CI, 28.7%-29.7%) of reported work weeks were more than 80 hours per week

> 12.1% (95% CI, 11.8%-12.6%) were 90 or more hours per week

> 3.9% (95% CI, 3.7%-4.2%) were 100 or more hours per week

> reported mean work duration decreased 5.8% from 70.7 (95% CI, 70.5-70.9) hours to 66.6 (95% CI, 66.3-66.9) hours per week (P<.001)

> reported mean sleep duration increased 6.1% (22 minutes) from 5.91 (95% CI, 5.88-5.94) hours to 6.27 (95% CI, 6.23-6.31) hours per night (P<.001)

> reported mean sleep during extended shifts decreased 4.5%, from 2.69 (95% CI, 2.66-2.73) hours to 2.57 (95% CI, 2.52-2.62) hours (P<.001)

This directly contradicts official data published by the accreditation council, which claimed compliance rates were much higher. Apparently, people lie about the hours they worked because they don't want their programs to be shut down:

> residency programs and residents themselves face a direct conflict of interest in acknowledging violations to the ACGME

> because the identities of those reporting violations have not been adequately protected in the past

> Because disclosure of violations to the ACGME could lead to loss of program accreditation, disclosure could threaten residents' own careers

Similar conflicts of interest seem to arise in pretty much every field. Speaking up about violations or taking companies to court appears to harm employees in the long term. The problem is probably much larger than what we're seeing.
I've been a React fanatic for several years, so my opinion is colored by that:

1. Great DX (developer experience) - a single language (Dart); no need for JSX, JavaScript, JSON, Flux/Redux and various other libraries. You can focus on the business logic rather than battling the ecosystem.

2. A single set of components (no iOS or Android specific navigator components etc.)

3. No longer need a JS engine to run - truly native

4. As fast as promised
enabling communication (e.g. ops for Mastodon communities) for labor unions strikes me as a better means of addressing the basic issue --- i.e. "the man" taking advantage of the little guy, intentional or not.

if time-tracking somehow solves the bare moneys/hour problem, other, perhaps worse, conditions could surface (thinking of what it's like to work in an online shop warehouse here, in particular, where time-tracking is .. not a complete "solution.")

traditionally, afaik, unionization is the way out of situations where a great number of workers are disadvantaged by some policy set by a few people in the industry.

this is a social [(science)?] problem, not a technological one.
I would not recommend this unless you hire these people for a regular maintenance role.

Leaving a box with no monitoring and no on-site skill capable of fixing it is a bad idea. That box will explode at some point and it's going to explode at the worst possible moment, and you'll loose tons of business (and/or data) while you scramble to get someone to repair it.

Unless you have people ready to jump in and fix it should it break, don't risk it and just let Heroku handle it.
>> Also the Syria and Yemen are civil wars. Don't know how you think it's reasonable to pin that on the "US, NATO and friends".

> Though I think you can put much of the blame of the civil wars staring on the US, even if you disagree the wars are still dramatically different than it would be without US support.

I think that's profoundly ignorant and belies lazy thinking, especially in relation to Syria.

The precise cause of the civil war was the domestic policies of the Assad regime [1] [2] [3] [4].

As for "providing the various sides with arms and support," I would be gobsmacked if you could show the US provided arms to Assad, especially in significant numbers. I recall significant dithering by the Obama administration over the level of support to give the rebels, and the fact that the US withheld arms to the rebels (over fears of inadvertently supporting Islamic extremists) is what allowed ISIS to grow so strong and eclipse the more liberal rebel groups.

> the wars are still dramatically different than it would be without US support.

If only because the support of other nations would have had a relatively greater effect [5].

[1] https://en.wikipedia.org/wiki/Course_of_events_of_the_Syrian...

[2] https://en.wikipedia.org/wiki/Timeline_of_the_Syrian_Civil_W...

[3] https://www.nytimes.com/2011/03/26/world/middleeast/26syria....

[4] https://carnegieendowment.org/2016/11/22/syria-s-path-from-c...

[5] https://en.wikipedia.org/wiki/Foreign_involvement_in_the_Syr...
I don't think he really understands the full implications of modern warfare between global powers. He's likely thinking in terms of firearms and tanks. Maybe some airplanes.

He's in for a big surprise.

On the plus side, the surprise will be quick.
The problem lies in choosing where to draw the line. People often assume the acronyms they use every day are well known, and don't think it's necessary to expand them. Case in point, you don't define APA, because you (correctly) assume I know what it means.

This article doesn't look like it was written for newcomers to the field; it appears to be written for hobbyists interested in having yet another cheap SDR at their disposal. The target audience knows the acronyms, so the article doesn't bother to expand.
>I'm pretty sure Android uses Google's DNS and that is hard to change.

DNS66 from the fdroid store. Doesn't require root either.
> but the broad outlines of positivism are widely accepted by scientists and engineers.

I don't think anyone doubts that a positivist framework is useful for science and engineering, but why should it hold elsewhere? Scientists and engineers are also stereotypically bad at social skills and politics. Perhaps because a different, non-positivist epistemological framework is required to thrive in other fields?
They are talking about the culture and values, not the weapons used to defend those things.

I'm not saying I agree that war would be good.
"Ritual" is jargon. Any archaeologist would understand that referring to something as "ritual" means "we can't explain what it is used for." It's unfortunate that the jargon is extremely easy to understand for non-practitioners, but that's not entirely unusual [1].

It should be noted that "ritual" doesn't exactly mean "we know nothing." It presupposes that there was a reason for something to exist, but often we don't have any insight into what that reason may be.

[1] The case that shows up in my work, writing compiler optimizations, is "global" which refers to optimizations that apply to the entire function as opposed to basic blocks or regions at a time.
I would dispute the reasonableness of that law... Does it apply to cherries, olives, avocado, apples, pears, etc.?
Show HN: Mashup, a Go CLI tool to generate random text from a list of websites
How Do Aliens Solve Climate Change?
I'm surprised nobody is talking about Express for the back end. Maybe it's because I hail from the front end world, but I'm already so comfortable in javascript I'm faster in it than if I had to learn anything else.

For the front end, I like Vue because it's just react with less boilerplate.
A large portion of the apps are intranet thing, instead of Internet. Business apps that are used in house.

Plus almost all websites are a kind of web app. And these have a complex backend for managing the content. While we browse the front end.
Anyone able to find any data on time 'til accuracy? I don't see it (even in the video linked in another comment).

Sure it's nice to "achieve 90% scaling efficiency" in images/sec, but images/sec alone doesn't get you where you want to go. Increased accuracy per unit wallclock time is what you want.
My preferred solution is Waxx https://www.waxx.io - It is Ruby and very fast. Mostly functions, no classes. Deploy like this:

waxx deploy stage
or
waxx deploy prod

The deploy script can be as simple as:

cd /path/to/folder && git pull && waxx migrate && waxx restart

Disclaimer: I am the author of Waxx and I wrote it to be as simple as possible yet still high performance and flexible.
story about 700,000 warblers and the only picture is of a single warbler? Come on NYT!
Since there has been interest in my story I'll tell another part of it. When we first discovered the distributor was copying us we sent them a letter telling them we had a patent and to stop. It did no good.

When we met with the lawyers they told us we made a big mistake. We were admitting we knew about the infringement. This sealed the issue of losing the patent. If we had acted ignorant we could have argued later we didn't know about it.
They should fix their mess, so it would work in Wine[1]. Or better release it for Linux to begin with.

1. https://github.com/roblox-linux-wrapper/roblox-linux-wrapper...
I would seriously consider Xamarin. The tooling with ReSharper is great. LiveXAML gives you the same instant reload that React Native has.

Xamarin Forms gives you a cross platform UI, but you can use fully native Fragments/ViewControllers where needed.
I’d say the slowness of Ruby is really over exaggerated. For most web applications it’s good enough, and the speed of development (how fast you can ship) almost always outweighs any costs from it being slow.

You can always replace the endpoints that are slow with something written in a more performant language like Golang or Erlang later.

I’ve worked on all sorts of applications from corporate CRUD to mobile billing gateways written in Ruby (usually Rails), and in very few cases has Ruby itself been the bottleneck.
My guess is that it would be a tax write off.

They'd have little chance of securing that value in equity or whatever, and probably impossible to claim it as revenue.

I mean they could do those things but it would be crazy.

But they could try write off a 'loss' (something of value they gave away) as a tax shield.
Here's the repo for that app I created with NativeScript:
https://github.com/BinaryNate/voxophone
Thanks for the response. I have to bookmark all of the links.

Yeah, It's been a long time since I even looked into databases and I am blown away by the innovation that has happened in this area.

Going back to Elastic Search, they have a pretty good hour long introduction video if you register with your e-mail. Also, they use BKD trees for storing numeric and geo data. I found an article which also links to the original paper on it

https://medium.com/@nickgerleman/the-bkd-tree-da19cf9493fb
so this isn't really an alternative to RN right now. As for basic features you have to know native development.
Usually CherryPy, Mako and MongoDB. Its how I won TADHack Mini 2018. I was able to focus on getting things to work more than how they work. CherryPy is older than Flask and OO based. Mako is a performant templating library that Reddit used and still might. MongoDB is just a document database so schema that changes isn't a big deal aka perfect for prototyping.

However I am making a shift to using D so I am learning DiamondMVC which is inspired by ASP .NET MVC and takes full advantage of Vibe.d and all the rest of the D ecosystem is available to me as a result. If I need something done in a weekend CherryPy and Mako with any DB.

If I wanna get something quick that I wont have to worry too much about scaling then D with Vibe.d or D with DiamondMVC is great. The best part about D is there is no crazy learning curve like Rust and it is very highly performant. Also the VS Code plugin is nice enough to make me productive enough.
Neuraxio Consulting – Take action on your data
Xamarin is awful. Incredibly slow tooling and useless UI libraries.
Xamarin has a good reputation too.