US
Haha
Size: a a a
2020 May 14
US
Well, I did have atleast three complaints, so...
IK
We are still using Moment.js 🙈
🦜
Чет орнул с уведомлений от авиасейлс
утром цена на билет упала на 1к
сейчас цена билета выросла на 1к
утром цена на билет упала на 1к
сейчас цена билета выросла на 1к
AS
Чет орнул с уведомлений от авиасейлс
утром цена на билет упала на 1к
сейчас цена билета выросла на 1к
утром цена на билет упала на 1к
сейчас цена билета выросла на 1к
Успел купить?
🦜
Успел купить?
Не, я не хочу обсервацию 2 недели проходить
🦜
пока не вижу как наебать эту систему
AL
Tell me everything wrong about Luxon 🙈
haven’t used it, and haven’t used momemt much recently.
It’s not “wrong” per se, but the API looks kinds strange. So.much.chaining.Why.so.much.chaining I know many assert libraries are reliaing on chaining, too, and though it looks kinda slick in examples it’s very annowying to use.
example:
yes it’s cute. But it’s super anoying to type because the whole chain of properties/methods is expressing the single concept. One concept = one methog call.
I looked through the API docs for Luxon and there are methogs that take object hashes to do the same thing as the method chain on your home page. I think you should focus on that.
Also, stringly typing leaks in some cases: DateTime.endOf(‘day’). Why is ‘day’ a string? Why is it not .endOfDay()?
I took a quick glance over date-fns. Their examples in general look like this:
1 function, 1 operation. No chains, no wrapping objects. No BS.
You do stuff right: you rely on Intl and polyfils, you keep the library small, etc. But as it is now I’d pick date-fns over Luxon.
It’s not “wrong” per se, but the API looks kinds strange. So.much.chaining.Why.so.much.chaining I know many assert libraries are reliaing on chaining, too, and though it looks kinda slick in examples it’s very annowying to use.
example:
expect(x).to.be.deep.equal.to(y)yes it’s cute. But it’s super anoying to type because the whole chain of properties/methods is expressing the single concept. One concept = one methog call.
I looked through the API docs for Luxon and there are methogs that take object hashes to do the same thing as the method chain on your home page. I think you should focus on that.
Also, stringly typing leaks in some cases: DateTime.endOf(‘day’). Why is ‘day’ a string? Why is it not .endOfDay()?
I took a quick glance over date-fns. Their examples in general look like this:
import {operation} from ‘date-fns’
const changedDate = operation(Date);1 function, 1 operation. No chains, no wrapping objects. No BS.
You do stuff right: you rely on Intl and polyfils, you keep the library small, etc. But as it is now I’d pick date-fns over Luxon.
EL
пока не вижу как наебать эту систему
в Сочи? лететь из Калуги
🦜
в Сочи? лететь из Калуги
неа
US
Andrey Listochkin
haven’t used it, and haven’t used momemt much recently.
It’s not “wrong” per se, but the API looks kinds strange. So.much.chaining.Why.so.much.chaining I know many assert libraries are reliaing on chaining, too, and though it looks kinda slick in examples it’s very annowying to use.
example:
yes it’s cute. But it’s super anoying to type because the whole chain of properties/methods is expressing the single concept. One concept = one methog call.
I looked through the API docs for Luxon and there are methogs that take object hashes to do the same thing as the method chain on your home page. I think you should focus on that.
Also, stringly typing leaks in some cases: DateTime.endOf(‘day’). Why is ‘day’ a string? Why is it not .endOfDay()?
I took a quick glance over date-fns. Their examples in general look like this:
1 function, 1 operation. No chains, no wrapping objects. No BS.
You do stuff right: you rely on Intl and polyfils, you keep the library small, etc. But as it is now I’d pick date-fns over Luxon.
It’s not “wrong” per se, but the API looks kinds strange. So.much.chaining.Why.so.much.chaining I know many assert libraries are reliaing on chaining, too, and though it looks kinda slick in examples it’s very annowying to use.
example:
expect(x).to.be.deep.equal.to(y)yes it’s cute. But it’s super anoying to type because the whole chain of properties/methods is expressing the single concept. One concept = one methog call.
I looked through the API docs for Luxon and there are methogs that take object hashes to do the same thing as the method chain on your home page. I think you should focus on that.
Also, stringly typing leaks in some cases: DateTime.endOf(‘day’). Why is ‘day’ a string? Why is it not .endOfDay()?
I took a quick glance over date-fns. Their examples in general look like this:
import {operation} from ‘date-fns’
const changedDate = operation(Date);1 function, 1 operation. No chains, no wrapping objects. No BS.
You do stuff right: you rely on Intl and polyfils, you keep the library small, etc. But as it is now I’d pick date-fns over Luxon.
Nice
FL
в Сочи? лететь из Калуги
А подробнее
FL
То есть сецчас реал можно в сочи полететь?
EL
А подробнее
ну в обсервацию забирают только со столичных рейсов
FL
Без всяких там пропусков и тд
FL
Я думал вообще ниче не летает 😂
EL
Без всяких там пропусков и тд
да, но смысла нет. гостиницы закрыты, кафе закрыты, курорты закрыты
🦜
То есть сецчас реал можно в сочи полететь?
можно, но если ты москвич, то отправят обратно
FL
можно, но если ты москвич, то отправят обратно
М-да
EL
можно, но если ты москвич, то отправят обратно
не если москвич, а если самолёт из москвы или питера