MarHoff

What's bothering me the most is that he claim facial recognition is involved while no evidence at all is provided in the body of the article.

Look like a plain old identity theft with the ID card he lost... As long as they recon his innocence after "humanely comparing" his face in a police station with video footage what would actually worth 1 Bn$ ???

A few year ago a coworker of mine was often contacted by police because his car plate was used by a matching stolen car... It was embarrassing but he didn't sue the car-maker as far as I know...

Also please read this fine lines it might be very interesting for some:

>If you believe your MacBook or MacBook Pro was affected by this issue, and you paid to have your keyboard repaired, you can contact Apple about a refund.

But isn't that a new behavior? Before I subscribed 1-2 year ago I read small characters pretty carefully, and in my memories in such case the behavior was to lock the previously private repo in a read-only state. Switching back to pro would then have restored full functionalities and setting on theses privates repos.

Automatically making it public seems like a new behavior, could someone confirm/infirm my memories?

iPhone are still sold today with bundled wired headphones.

Since when proposing a sold separately wirelesses alternative is "forcing you to go wireless"?

The thing is I have the "hellishly flawed MBP 2016", I carry it daily into my messenger bag over bike/train/feet (often running to catch train) in a separate pocket but without other protection. It fell on the floor once from table height with lid open and ended up with a very small scratch on the corner but totally ok otherwise (and it was totally my fault).

Everything is perfectible but to say it's not a good and resilient design as compared to other laptops is just non-sense. Nothing is 100% fail-proof we must be realistic.

I had issues with apple products, but nothing so bad that a visit at a genius bar couldn't solve in a reasonable manner. Yet I will loose trust the day they let me down in an intolerable way, but surely not based on hearsay's from the web.

There could actually be a sweet spot for ApplePay (and similar service) there. Quick anonymous and secure tips for website.

Guess I have a "localized" deformation as french keyboard include a ! character accessible without any key modifier, so it's actually pretty straightforward to use.

With DuckDuckGo you can always use the !g syntax to switch to google if first results don't suit you need.

By my experience DDG usually provide way more appropriate answers when you are looking for a reference or a documentation entry. Google still is better for recently pushed contents like news and is still marginally better for finding result inside Q&A sites. After 1-2 years of DDG by default I tend to know in advance which query is best for which search engine and so I half conscientiously add the !g while typing when needed.

The saddest part being that the film industry is even further behind. Some contents are still totally unreachable by any legal offer outside their home country.

My personal rule of thumb is that if I look for a reference manual or an official website vanilla DDG is the way to go. If I'm looking for really fresh contents like news or latest QA !g gives better results.

Guess it's logical because even if the search algorithm of DDG is pretty neat, they can't compete yet with Google army of crawlers that probably use every idle computing power of their massive cloud.

Non english speaker here you mentioned an OSS solution called "Inbulk" or something like that during the conversation. Could you spell it I'm pretty interested in finding out more about that project but google return a lot of unrelated result because of the name I guess...

I think the point is to provide a set of tools for people that build data pipelines. Period. The software being open source don't reflect in any way WHO will use this tool. Depending on the success of this project, it might be that you could switch your team to this new tool at some point.

Personally I work as a "lone wolf" (to my own complains) because I'm in a small company that can't afford a huge team. Most of my (ETL) Transforms are done in SQL which happen to be pretty standardized as opposed to many ETL products I've seen so far.

This solution is probably far from being ready, but I find this approach quite interesting, because it look like a code based ETL that use SQL for transform (so I might be biased). Overall this might result in a more maintainable/versionable data pipeline model than GUI-first ETL which usually generate spaghetti code. Because you are usually forced to regularly adapt data-pipeline to unstable external inputs, being able to easily diff ETL process would be a blessing.

Thing is they are competing with PostgresSQL which you can extensively try for free before opting for a support.

"Free" being already hard to beat. The fact that you can't extensively test a solution is a real turn down for me (unless negotiating with commercials which is not nerds cup of tea).

With arrays and composite type the potential for semi-structured schema was there for decades. The concept just got more mainstream with NoSQL, more easy to maintain and more efficient with indexables type such as JSONB.

I somewhat disagree, the author is perfectly aware that putting this code out can cause security issues and is willing to accept patch when necessary. For example 9 hours ago he added support for windows in responses to reported issues. Please take time to read contributing rules before complaining about a totally legit FOSS project:

All changes are welcome as long as no code is involved. If you run into any bugs, please file an issue and explain how that was even possible.

So I kindly invite you to discuss this issue directly with the author through GitHub issues manager as he had invited you.

I agree with you, but I think you did overthink his metaphorical example a little.

I think the point was that for a 40 people club odd are very very poor that two people would have the same name. And even if so a club manager could still differentiate by adding a middle name or a nickname (in a 40 people scenario).

Of course IF your neighborhood club expand and you need to manage a lot of people you'll have to switch to a better technique. His point was that you must fit to you business case. (But hey some people change name when they marry so... problems can happen fast, but that's mutability issue not uniqueness).

Overall very good article but keeping critical mind as you did is needed.

Also you can't adblock paid top ranked search result so even if you don't click, and even if you know it's an ad, you've seen the brand in the top result, and the brand pay Google for that.

You just made me realized that this sentiment of pending apocalypse is maybe exactly what drove humankind forward along the past.

It just look like the notion is always morphing from generations to generations : the flood, the plague, the apocalypse, the nuclear winter and now climat change.

From biblical hazards to scientific hazards, maybe humankind is finally like the high school student who only work great when under heavy pressure for it's exams.

And maybe just maybe this is how you can best reconcile science with religion because no matter your beliefs, this is a test for all of us... Are we making enough "good" around to deserve joy for us, our children and all they children after them?

Well I'm more a user than a developer but I already have helped others users by responding to issues in someone's else repo.

Recently I've opened an issue on a project I really appreciate, and I'm so sorry I don't have time right now to help the developers solve it. And so I don't blame them either.

When I'll have more time/skills I will totally stick around, keep giving feedback and maybe propose PR if he hasn't solved the issue by then. But I really don't feel like signaling a serious issue without PR was spamming them.

And who know maybe I'll become a contributor one day if I can. But right now, had I been "forced" to submit a Pull request I would have either submitted a really crappy one or more likely censor myself...

Here is the issue if you feel like having a look : https://github.com/pgRouting/osm2pgrouting/issues/167

You just made my day!

Didn't knew Ctrl-Shift-Up/Down how can I've been coding without!

At the time of the location gate I had parsed my personal buffer and I found out that pretty much all Manhattan was included. I hadn't a roaming plan when visiting New-York so I only got randomly access to internet at free hotspots.

So I guess a good rule of thumb would be to turn off while on the road with no wifi, but keep on in cities (where A-GPS is the most efficient) where you gonna stay for awhile with sporadic hotspot access.

Also classical GPS (while slow to kick-in) is often really good enough in countryside where you don't suffer from building shapes interfering with the signal.

That was at the core of the "locationgate" a few years ago because location of surrounding access point wasn't flushed enough regularly. Hence revealing approximate location to people that can materially access the phone (this was before iOS full disk encryption). See: http://allthingsd.com/20110427/apple-breaks-its-silence-on-l...

And by today standard I really appreciate Apple approach of doing most of the computation on the phone itself.

I like your schema-lite terminology and I think it describe pretty well my approach.

I've only start to explore all possibilities, but main use so far:

-Store experimental properties before next schema revision

-Particularly good alternative to composite-type in early stage dev if you want to make live modifications without replaying the whole deployement script. (Composite type usually have huge cascading constraints)

-Storing "metadata row" for later use

PS: Actually it may even be an alternative to composite type in production because I can totally picture case when you need row level "objects" that vary depending on the value of another column. Yes you can normalize, but it might be more maintainable to keep everything in one table an write an appropriate check constraint. And it will still be easily human readable as opposed to a literal representation of a custom type or whatever (think of PostGIS geometry type that is very versatile but totally opaque to humans).

I think you are mistaken, even if implementation will vary you can have the same behavior (However I won't ever try in production because jsonb base FK is a pretty scary concept IMHO)

However on a solution I've implemented on PostgreSQL I expand jsonb as regular field in a view and made that view editable via trigger. This way users can update jsonb_field without being aware of because they edit it through a view as if they are normal fields.

functions are actually functions...

Sorry if I was unclear, I'm not advocating for ORM.

And yes it breaks down because it is similar but different. Row "instances" can perfectly exists outside a table and even be defined outside any table via composites types or even on the fly.

Just saying a RDMS can be a powerful object-oriented environment using solely SQL and no ORM at all.

But do schema-less implement foreign constraints at all????

I'm currently implementing a mixed solution where clearly defined properties (and thus ID) have columns and constraints but I also include a schema-less "all you can eat" jsonb field so that experimental properties can be stored.

Upon each release I will migrate validated shema-less properties to static columns or even sub-tables. Similarly if a column is remove on next iteration I might transfer attributes to the jsonb to revert it later if needed. This does include a migration step but this seems only like good practice. Of course scaling... but I'm really not limited by this now.

The client will interact with the model through views or functions so that he don't have to care if columns are real or not. But anyway as soon as PK/FK are needed I will probably straight-out think that jsonb will be insufficient and take 5 minutes to think of a relational way to implement.

Use jsonb inside a Database and use constraints to ensure all requested json attributes (store name,etc..) are present at INSERT/UPDATE time?

That don't seems like rocket science to me... duh...

PS: But of course don't store ID in an object value or you will lost major benefit of RDMS relational constraints.