skysight-inc/HackerNews huggingface dataset:
> A system or component relying on obscurity may have theoretical or actual security vulnerabilities, but its owners or designers believe that if the flaws are not known, that will be sufficient to prevent a successful attack. Security experts have rejected this view as far back as 1851, and advise that obscurity should never be the only security mechanism.

https://en.wikipedia.org/wiki/Security_through_obscurity
Same here for me and my wife. We only haven't bought the PS4 Pro because we can't find enough place to put the couch but we're working on that.

Many modern PC games imitate the mobile games monetization model and are increasingly hostile to any semblance of long-lasting community. Throw in the mix the clueless multiplayer implementations of many games where people are as toxic as it can get and it's easily understandable why so many people leave those games when the novelty wears off.

We're gonna transition fully to console [and partially to PC] single player games with good stories and graphics (Lara Croft, Horizon: Zero Dawn, God of War come to mind) -- as soon as we handle our logistics problem.
> expect it to be local, which means face to face talking with business owners

When I first started out writing database applications with Clipper, that's exactly how I operated. It's very satisfying to work with local people helping them with their problems.
Thanks for the Slinky reference, I had not seen it before. I spent some time evaluating Scala.js a few years ago and liked it, but ended up not using it. When I retire from my full time job in a few months I am planning on reworking/rewriting a few of my web apps and I will do an evaluation of Scala.js with Slinky.
This is Chromium-based, so is part of the largest user base, and because it's downstream it will always be at least a bit out of date.

I think there are lots of useful things alternative browsers could do, and I'd like to see some succeed, but this problem seems difficult to get around.
> While recommended, `with` isn't always applicable. For example, assume you have an object that encapsulates some sort of a database that has to be committed and closed when the object ends its existence. Now suppose the object should be a member variable of some large and complex class (say, a GUI dialog, or a MVC model class). The parent interacts with the DB object from time to time in different methods, so using `with` isn't practical. What's needed is a functioning destructor.

Isn't the issue with __del__ that you have no idea when or even if it will ever run? This is always a problem with destructors, no? I know I'm slightly too paranoid about resource management but I get nervous with that lack of control.
Well, there is only one way to know if he/she will guess the reason :)
some scientists (wrongly ) think they can trick nature .... this constant manipulation with synthetic drugs is getting human kind clise and close to extinction .... and they know it #savethemall is the silliest way to go
Can't unlock an Android phone?Just take a Skype call: App allows passcode bypass
People are assholes to smokers. Like, it's socially acceptable to be assholes to smokers these days.

I've had random people on an almost daily basis harass me for smoking. Flicking my butts on the ground was a big fuck you to all of the non smokers that harassed me.
PostgreSQL is a good default choice because it is rigorously engineered and offers a wide variety of production equality extensions that mold it into whatever you need it to be.

If, halfway through your implementation, it turns out that you need to store GIS data or time series or you need a key-value document store, Postgres can easily do all of that, and you can have everything in one DB (unless it turns out that your requirements are truly special).
Check out realworld.io, like TodoMVC, but for full stack apps.
Some recommendations in this pdf are sooo vague and lack proper context. For example, what the hell does this mean: "Let the Code Make the Decisions: There is no need to spell everything out in minute detail".
Current state of the controversy, with links to papers, here:

https://arstechnica.com/science/2018/12/two-independent-anal...
"The truth is that a vegetarian diet can provide sufficient protein requirements for humans"

Maybe all carbohydrates are basically all the same, but you can't say that about proteins. From them you get essential aminoacids, and even if you can get all/most of them from vegetables, you should be careful to not miss some of them having a narrow vegetables selection.
From their FAQ:

>What about the sonic boom?

>Boom's airliner is designed to maximize efficiency while producing a “boom” at least 30 times quieter than Concorde's.
...
Meteor + React + MobX + GraphQl + MongoDB
> Prefer code to comments

I used to make this same argument, and then took it overboard by never commenting. After reading some literate codebases, I’ve changed my mind.

Code is (almost?) always obvious to you as you are writing it. So, you never recognize code that is in need of a comment until you come back to it and struggle to understand its purpose and the context that gave it birth.

I now follow a rule: a meaningful comment at the top of each file. A comment on every exported function / value. Often, in the process of writing the comment, I realize I’ve poorly named something or that I’ve failed to handle some case. Comments help guide the reader, but also the writer.
"Would you be happy to have your tax return displayed for everyone to see? In Norway, no one can disguise their earnings, as every citizen's is made available for everyone else in the country to inspect. Workers can see what their colleagues earn and neighbours can snoop on how much the people next door make — all legally and online.

On a date every year in October, just after midnight, Norwegian citizens' annual tax returns are posted online — and the country's Norwegian newspapers leap to produce top ten lists of the country's highest earners, the incomes and taxes paid by the political and cultural elites, celebrities and sportspeople.
https://www.theguardian.com/money/blog/2016/apr/11/when-it-c...
Hi-Ten Bomberman
They're very specific, you seem to be rather disingenuous in this line of argument. It's very easy: human-rights violations with thin legal justification, sure - routine low-level stuff like petty theft and copyright infringement, probably not. The decision makers there are biased towards exactly the kind of person that would murder for a perceived greater good but wouldn't park out of bounds.
Yeah, see - I've had a great deal of experience with smokers, including my close friend past me. People who smoke get high on tobacco, which makes them feel good. Right? Well, it makes them feel good even when they're crapping all around them and then they're all surprised.
Caffeine is obviously s performance enhancing drug. The ncaa has limits to how much caffeine you can have in you while performing, I’m sure other entities do as well.
Does the old libc not compile on the new system anymore? You could install it on the side, link to it, and fix up paths if needed.
I cannot conceive of any future where the eventual upshot of all of this isn't...a Surface Pro.

The thing is, there is nowhere left for Apple to go. What else can they do with iOS? They will be forced to make iOS more powerful and that MUST include things like proper file management, multiple windows, displays, mouse support etc...aka a Surface Pro. Perhaps a more pleasing-to-look-at iteration than Windows 10, and better quality native apps, but a Surface Pro nevertheless.
Being an asshole to assholes... makes you an asshole regardless.
Interesting. Do you happen to have examples of these templates?
Short, but efficient days at work:) That’s probably why the GDP per capita is a lot higher than in Sweden:p
Vanilla javascript (Yes I said it). Build a PWA and either PHP 7 or node for backend. Anything else is for you if you already have a preference.
If you didn't provide constraints (node/react), I would use the following. Please note, this is highly opinionated, so nothing to get offended or upset about. I like to keep my stack simple:

A. Simple static sites:

- Jekyll

B. Medium complexity, CRUD applications:

- Phoenix/Elixir
- Coffeescript

Note: With the latest version of Phoenix, you absolutely don't any JS frontends at all. Watch they keynote presentation for the liveview demo: https://www.youtube.com/watch?v=Z2DU0qLfPIY

C. Complex Web applications:

- Phoenix/Elixir
- GraphQL/Absinthe
- VueJs + Vuex + Coffeescript

Developing with Phoenix/Elixir is so much better than any of the node frameworks in the ecosystem - this has consistently been my experience. So, give it a shot if you can.
> How do programmers here account for the unexpected?

This is where good architecture and design come into play.

Design for what you know and need now but use good principles (OO, etc.) so that code can be modified in a sane way.
Yep and while it might start with a simple website, after you deliver on that and start hanging around their business you might be able to think of ways to improve how they operate their business.

Such as scheduling clients, inventory management or dealing with whatever problems that company has with software solutions. Before you know it, you're picking up 3 month programming contracts.
Simple Redux–a bare-bones redux implementation for teaching purposes
> I figure at least I annoyed them

And this is why they continue to do it. You get a response of indignation when you order random strangers in a free society how to behave. You'll get better results if you use guilt instead of demands.
I find this a very good idea, but since the latest news update was 2012, how has Sanos kept up with security vulnerabilities?
All the iPad reviews on youtube, Marques, Dave2D, the Verge...they were all crying out for a chance to fully exploit the blindingly fast A12 chip with software to match. Specifically multiple displays and mouse support.
"Privacy, as we understand it, is only about 150 years old."https://medium.com/the-ferenstein-wire/the-birth-and-death-o...
this is probably just because there is a pop-up dialog box the secretary sees when she puts in the request, and they are obligated to ask. there is no answer that will result in your request being declined, including "I'd rather not say".
An addictive “murder map” of medieval London
> UI experiments like this show that what a lot of pro users want for iOS on the iPad is for it to become a Mac.

I have a hard time understanding this. Why make the iPad into a Mac? If that's what you want, then get a Mac.

My gripe with the iPad is that on larger screens, the somewhat sparse grid of app icons seems a little silly. They could at least increase the density.

I hope they don't change the character of the iPad because right now it's my favorite computer to use.
I wonder what a world where molecular level tagging of products combined with penalties for illegal disposal would look like?

I’ve also been seeing JUUL butts / fake USB drives piling up all over NYC.

They really ought to have a desposit or recycling program for those.
golang backend restful api, websocket service, frontend some client side SPA or static pages. database + redis for k/v and queuing, for heavy duty stuff rabbitmq.

the nice thing about golang is that i don't need containers because my runtime package is basically a binary, golang is great about cross compiling for various platforms, too. when i used ruby or python, i'd have to package up all the dependencies and even get the runtime interpreter installed while using some tools like rbenv, etc. really, really annoying.
Ah, nevermind that guy. I really like how Codea looks, and I think the iOS Menu looks great. More importantly, it feels great to use.
Try to learn templating engines like 'pug' and 'stylus', if you haven't. Writing vanilla HTML is getting so old and overly repetitive and they do a good job of making you type a lot less.

And also you should learn packaging to include dependencies by mentioning those in a single file. Parcel bundler has been working very good for me as it is fast (webpack is complicated and not fast) and incremental build is a fraction of a second.
C++ Parser in Forth?
Interesting - I’ll try it out, quite curious to see how it compares with Vivaldi, which has an Opera-like UI with the Chromium engine.
> Consider duplicate code to be a mistake

I partially disagree. Some of the worst code I’ve seen was an attempt to reduce duplication.

It’s easy, especially in UI code, to mistakenly identify duplicate code, and prematurely build a DRY “solution”. Premature DRY is the root of much evil.

I try to follow the rule of three before trying to identify duplication. Even then, I’ve become much more cautious than in my younger days.
can you elaborate on the distinction you are making between viewing and owning?
> Does it matter by how much?

That's the only thing that matters.
It seems to be they just don't like it.
A hacker “White hat” becomes legally rich
Title requires reference to this article being from July 2018
LiteCLI – A user-friendly command-line client for SQLite database
> what do you do to protect resources when people forget to use with statement?

In many cases it is perfectly reasonable to only allow context manager use. And if it isn't possible, offer explicit close() or dispose() interfaces, don't rely on __del__.
Or they could crack ahead in the manner described in the article.
Will it benefit to Radare2 and Frida?

https://github.com/dukebarman/awesome-radare2

https://github.com/dweinstein/awesome-frida
I'm surprised no one mentioned cybernetics yet. Author's premise seems to be that digital, centrally controlled systems are becoming pieces of systems made up of self-regulating sets of feedback loops.

The idea certainly isn't new, having been written about in the '50s in Stanisław Lem's "Dialogi". The observation about digital systems is certainly fresh though.
> It is highly opinionated unlike React

Agree on that point , I like Angular because it's opinionated compared to React.

> and backed by a giant unlike Vue

Strongly disagree , Vue is backed by many large corporations and unlike AngularJS was designed to guarantee backward compatibility.

AngularJS not being compatible with Angular is what has killed for good the frameworks and left thousands of entreprises in dust when they believed angular would become a standard because "it's backed by a giant".

Workings for banking sector , I've many customers build CRM or KYC applications on top of Nuxt. Developers love the Vue ecosystem.

> Seems like a safer enterprise choice.

Strongly disagree here as well.

Angular is a great framework but it has absolutely unacceptable build size,

A "Hello World" using Angular 7 with Ivy Rendering is 500KB+ ( tested this morning ). This is not acceptable for modern frameworks to be that big.

Vue and React stay largely under 100KB in terms of build size.

They are lots of scenarios where picking Angular over Vue & React would made things more complex for a project.
Redux still baffles me. I've implemented it 4 times, and it still confuses the hell out of me.

MobX is a much better fit for most react apps IMHO. Redux could be good, if you have a database [id] driven application, but for most people is way too restrictive.

If you are working in a small team, and are using Redux, you are probably making life harder than it has to be.
‘Simole website’ and ‘with react’, in my experience, is a contradictio in terminis. At least relatively. Just use server-side rendered html with rails as a platform and you will be building your actual website rather than hooking library after library together into some unmaintainable mess.
SQLite is great when there are few writes, such as for a personal blog. For lots of writes, you probably need another database.
You can go really far with node. I'm a node js and Vue dev these days, but I think we will end up switching over to React for public facing stuff due to ease of hiring and getting devs to work in it. I like sticking to one language, it performs pretty well, and is fairly easy to hire for and get help with.

I am looking at React on the front-end instead of vue, due to how much easier it is to hire for react.

The isomorphic/universal rendering is really awesome for node on the server, one set of templates vs two, plus it seems like the GraphQL stuff is way more mature on node. We're not currently using GraphQL, but having that option open to us is nice.

Combined with all the success stories from Linkedin, Paypal and even Walmart around moving stuff to node, it's also an easy decision to defend.

I'm not a huge fan of debugging node, that could be a bit improved, but overall I am happy with the choice to try to build everything in node unless there's a compelling reason not to.
Yes please do reupload it!
I'm a JVM fan, but I've never been able to find good tutorials on documentation on play. It seems like everytime I find a resource its for some old version that isn't compatible.

Do you have any recommendations?
Thus my "indirectly" modifier. A lobbyist cannot give $10,000 to the politician directly. They can give $10,000 to a PAC that is closed related to the politician.

The fund-raiser would also be legal. There is no masking of donations - those attending the fund-raiser do pay for their tickets. Nothing prevents a lobbyist from doing the legwork to make the fund-raiser happen.

Main point being, despite legal limits on direct donations, there are many ways a lobbyist can facilitate the flow of money from special interests into the pockets of politicians.
So, no touchpad mentioned.
I don't think that is a reason to not attempt developing new things.

And anyways, this is using the QTWebKit, my understanding is most of the security related aspects are from there. Since it is a fork of WebKit I imagine it gets security updates from there.
I am currently building a really complex application using Mobx, it’s great! Because of how it works you can do things that are impossible with redux - as the state would take too long to update with redux.
I’m also using mobx-state-tree which is like the love child of mobx and redux. Amazing project as well, should be used if you want to have explicit model validation and immutability. I used it to build a history feature - that would have been almost impossible with vanilla mobx.
> We dispatch instanced draw calls where each instance corresponds to a segment’s quad. The vertex shader finds all of the information it needs from the primitive offset and segment id of the quad it is working on.

Hm, any reason you're using instanced quads? From my understanding of how GPUs work, instancing only has big gains when you have a lot of vertex data in the draw call [0]. Instead of the instanced quads, have you considered making a vertex buffer containing two shapes: a + for the center/edges, and four quads for the corners. That way you could still do the whole thing in two draw calls, and you're not going through the slow instancing path. And if you have to blend the bg anyway (e.g. rgba background-color), you can just draw the whole vertex buffer in one go to skip the extra draw call.

[0] http://www.joshbarczak.com/blog/?p=667
Have you tried out SQLAlchemy Core without the ORM?

Regarding the joins:

j=t_user.join(t_address, t_user.c.id==t_address.c.user_id)

select([...], from_obj=j)
I made my statement about an individual because OP seemed to be asking as an individual, but it still applies perfectly to society; you can pretty much search and replace on the text:

"In this specific case, if society making privacy a top priority at the expense of everything else reduces everybody's odds of identity theft from 2% to 1%, I think a lot of people would say "I'd rather society priorotised having fun and accept the higher risk to society"; if a tiny lifestyle change across society could reduce the odds from 20% to 1%, the outcome would probably be different."

The point remains the same: you can't make sensible decisions without knowing the odds; avoiding all activities with non-zero risk means avoiding all activities, and that's why it matters how much.
Use Elixir only if this isn't going to turn into a team effort or you'll need your team to learn from the language.

And coffeescript is taken over by other transpilers like TS and even ES6 and above.

Check here for static site generators. There are good alternatives to Jekyll.

https://www.staticgen.com
Tldr:

Captcha -> request Audio verification-> download mp3 and send to google API for recognition -> 91% accuracy
I don't understand the point this article is making, and don't agree with the sentiment either.

One should not feel embarrassed for not knowing something and then asking more in order to learn.

The correct term is not embarrassment, it is inquisitiveness - which must be encouraged and not shamed
Great read.

To anybody that isn't very familiar with jazz in general and wants to explore it, I have a fun suggestion: Take your time to read Miles Davis' autobiography over the next few weeks while listening to some of the artists/music he mentions. First the Dizzy and Bird that he absolutely worshiped, and then his contemporaries that he liked and hated.

I've done this a couple of times so far and it's great every single time. It's hard to put that book down, and even harder to turn off the music.
>I cannot conceive of any future where the eventual upshot of all of this isn't...a Surface Pro.

Well, Ford's customers couldn't conceive of a future where the eventual upshot wouldn't be ...faster horses either.

>The thing is, there is nowhere left for Apple to go

Because we have exhausted UI paradigms and interaction design?

>and that MUST include things like proper file management, multiple windows, displays, mouse support etc...aka a Surface Pro.

The "aka a Surface Pro" is where you're wrong though.

All of what you ask for can be answered by "just buy a Mac laptop" today. There's absolutely no reason for anyone to want an iPad that does all that -- except to get a laptop with touchscreen hybrid. But those are not exactly some wide success in the PC world either.

The iPad serves a need without desktop-features. And it sells 10s of millions of units (10x or more than the Surface) every year without these features. The ability to get a desktop OS-X experience is not why iPads are bought.

Here's how it can play out:

E.g.:

- "Proper file management" can be abstracted totally from storage as far as the apps are concerned, like iOS already does, and have powerful metadata properties and searchability (the way Microsoft tried and failed with their WinFS project). So not like Surface of today, or regular Finder-like file management.

- Multiple windows can be non-overlapping, and develop into a tiling/snapping mechanism. OSes have already disfavored the once dominant MDI windows (and even third party apps have, e.g. Photoshop of yore with Photoshop of today). This can be a next step.

- displays, the iPad Pro already supports external displays.

- mouse support, this can or cannot be added, but if the table factor has to have any meaning it has to be secondary to the touch experience (so apps should be prepared to work in 100% touch mode).

More importantly, the main premise of the iPad is the hassle free device management. Apps are all sandboxed, the OS is dead simple to configure, zero viruses, everything backed to the cloud, etc. Those are the avenues that will be enhanced and expanded, not how to run IDEs.

It's not 'full customizability and power to run any niche pro app', it's 'it just works'. Pro apps will came (and in several sectors have come), but only by respecting the "it just works" part.
Fragility grows with size. The test speed of the downscaled version should be higher if anything.
Branson/Virgin wanted to but BA refused to sell the concordes they were scrapping:

>Virgin described BA's refusal to sell the planes instead of retiring them for good as "an act of industrial vandalism",...https://www.telegraph.co.uk/finance/2855774/Virgin-bitter-as...

Airlines don't go supersonic because there are no aircraft.