>Track hits on a post-download URL
It will be mixed with downloads that come from organic search.
>This stuff is mostly meaningless.
I disagree.
6,499 karma · joined July 5, 2010
It will be mixed with downloads that come from organic search.
>This stuff is mostly meaningless.
I disagree.
Also, Google Adwords counts conversions for visits for 30 days. Which means on the 1st visit from the ad campaign, there can be no immediate conversion (and that's OK). But if the same person returns to the website (not from the ad) and downloads/signs up that would be counted as conversion attributed to the ad.
Static site generation should be simpler. Currently it's over-engineered.
Wait until you get bombarded with ads in your "smart" car. It's coming, have no doubts.
It's not declarative. It's functional.
I believe that the approach that is followed by PRQL is more practical than SQL. We've implemented a similar approach in our visual ETL tool for non-technical people (https://easymorph.com) and it works wonderfully. Other cool things you can do with this approach (and can't with SQL):
* Modify existing columns without re-selecting the whole dataset
* Loops (iterations)
* Conditional IF/THEN/ELSE branching as a workflow statement
* Exceptions & error handling
Many our customers specifically looked for an on-prem solution as they don't want to deal with SaaS and its privacy issues and use-based pricing. With an on-prem tool like ours they get unlimited runs, unlimited data volumes, unlimited use for a reasonable fixed price.
I believe SaaS is overhyped and in a few years the trend will change toward on-prem SaaS-like apps and platforms.
While there are cases of obvious abuse of the subscription model, in general, the subscription model for complex software is here to stay. Simple, one-off applications that don't require support or further development may not need subscriptions though.
One day I will do it.
Speaking more broadly, whether we talk about HTML or PDF it's the same problem: documents should have two representations - human-friendly and machine-friendly until AI gets so good that only having the human-friendly representation is enough.
Web2 succeeded because Web1 protocols haven't been developed to withstand abuse. For instance, the email protocol (Web1) hasn't got an extension that would enable receiving emails only from authorized senders. As a result, email is heavily abused by spam and phishing to a degree that only a handful of large email providers can effectively deal with it. The centralization of email services is typical for Web2.
RSS (Web1) hasn't got an extension that would enable access restriction and following. As a result, centralized proprietary ad-driven social networks (Web2) took over.
HTTP (Web1) hasn't developed a micropayment mechanism. As a result, the current internet is monetized through all-pervasive ads (Web2) with all the terrible destructive downsides that come from ad-driven media.
Not necessarily. See https://xkcd.com/936/
Of course it wasn't. People didn't know many grim things about the country they lived in because their information intake was carefully designed to exclude anything negative about the USSR and the Communist Party. They believed they live in "the greatest country in the world". The decades-long propaganda has produced so profound and long-lasting impact that many people in post-Soviet countries (especially in Russia) born in the Soviet times still long for that feeling, 30 years after the collapse of the USSR.
It's now hard to say how frequently Amazon's infrastructure goes down. The incident rate seems to have accelerated.
[1] https://en.wikipedia.org/wiki/Sonchus_fruticosus
PS. Ok, it's technically a shrub.
Serverless. Current clouds are a half-step because they partially abstract away hardware. Serverless is the ultimate cloud because it abstracts away all hardware.
Self-hosted open-source alternatives to public clouds. Public cloud providers use proprietary software to provide and manage cloud services. However, open-source alternatives will eventually appear and will only require a pool of machines (virtual or not) to operate in order to provide a set of cloud services - computation, storage, identity management, load balancing, etc. This will lead to decentralization and proliferation of private self-managed clouds.