51–58 of 58 posts
Earlier quoted context omitted.
it sucks - but i think a better option is to use a charity to do this rather than give 'em cash. You lose taxes twice - once from your own end, and once from the restaurant's end.
I don't think you can "donate" to a for-profit private business without paying taxes...
Earlier quoted context omitted.
I don't think you can "donate" to a for-profit private business without paying taxes...
no, i meant donate to a charity, whose sole purpose is to help those businesses in need. You don't donate directly to the business (which is the tax hit).
Earlier quoted context omitted.
no, i meant donate to a charity, whose sole purpose is to help those businesses in need. You don't donate directly to the business (which is the tax hit).
Are charities allowed to give assets to for profit corporations?
Earlier quoted context omitted.
I've asked someone who likes using tons of JavaScript before and the response I received was along the lines of "It saves developer time." I don't get that one because in my experience, writing straight HTML is simpler than writing JavaScript. The real problem seems to be that many people today seem to have learned frontend web development through fancy JavaScript frameworks and don't know any other way. Since learni…
i don't know if i would have made the same choices they made, but I've been developing websites since 2000 (so before one relied on JS for anything but sugar) and I prefer to work with the component model of things like webcomponents, react, etc than I do with plain HTML. So it's not just about "i don't know how". I just think it fits my mental model better.
In those many cases when the page just carries information - it's not, for example, application-in-page, where you can change parameters and see the results - it's a document. A document is simpler than an app, doesn't need full power of Turing complete engine, and because of that, allows easier tools to manipulate - extract data, render differently (like for users with disabilities), modify (e.g., combine with another data set).
Sure, documents can be considered apps - a simple version of apps. There are also reasons to explicitly maintain strictly lower complexity for something which is not a proper app. For those, webcomponents could be overkill. Just imagine webcomponents with which you never use at least some of their capabilities?
This is not the time for feel-good charity and small scale philanthropy
Earlier quoted context omitted.
i don't know if i would have made the same choices they made, but I've been developing websites since 2000 (so before one relied on JS for anything but sugar) and I prefer to work with the component model of things like webcomponents, react, etc than I do with plain HTML. So it's not just about "i don't know how". I just think it fits my mental model better.
Do you approach pages as applications or as marked up documents? In those many cases when the page just carries information - it's not, for example, application-in-page, where you can change parameters and see the results - it's a document. A document is simpler than an app, doesn't need full power of Turing complete engine, and because of that, allows easier tools to manipulate - extract data, render differently (li…