389
results for "microformats hard"
-
↩️ It's in the middle of the process doc http://microformats.org/wiki/process#:~:text=property%20name Naming is hard, and coming up with a shiny new name that no-one has ever used before is not usually a good idea.
Loqi
at
2020-06-17 12:20
-
We write standards in the imperative mood, and it's hard to know how to get there.
[KevinMarks]
at
2020-06-09 23:12
-
(often the opposite, because it's too hard to maintain the "pretty")
[tantek]
at
2020-06-07 22:29
-
Because it is a hard-coded number
GWG
at
2020-06-06 23:19
-
I spent a little time on the Microformats theme....half the function calls were deprecated in WordPress 2.8.0, so most of the job is replacing old functions with new ones, removing hard coded values with WordPress functions...
GWG
at
2020-06-06 21:03
-
↩️ RSS is dope but I think since it requires so much extra tooling, it's hard to work with. I've leaned on using microformats2 to give my HTML pages the same RSS-y vibes but without having to make a separate page. So much easier IMO. https://microformats.io/ + https://indieweb.org/h-feed
Loqi
at
2020-06-01 09:45
-
Writing documentation is hard. So many notes on that document about already outdated sections
Zegnat
at
2020-05-12 19:53
-
The PHP parser has had different whitespace handling since mid-2018, and I feel like many have been using it without issues since then. Sadly it means the test results are extremely hard to grok
Zegnat
at
2020-05-09 19:10
-
But will have to wait for the morrow. Sleep time for me :) Thanks for all the hard work, again!
Zegnat
at
2020-05-03 01:12
-
The composer.lock file takes the set of dependencies, and puts a single pin/thread through each one that strings together a working valid state. It may bite hard in future days when composer.lock is missing.
cjw6k
at
2020-04-30 22:04