Notices tagged with java

  1. Now seen in context. Did you use # or # in your recent research presentation? Could the language used be a factor?

    Friday, 09-Feb-18 16:40:16 UTC from gs.kawa-kun.com
  2. Now seen in context. Did you use # or # in your recent research presentation? Could the language used be a factor?

    Saturday, 27-Jan-18 11:25:11 UTC from gs.kawa-kun.com
  3. No, nothing that would be helpful. Current or former # product, targeted below #, above # Every time I see # mentioned, I also see # I've never seen it in use anywhere.

    Wednesday, 27-Dec-17 10:55:10 UTC from gs.kawa-kun.com
  4. Now seen in context. Did you use # or # in your recent research presentation? Could the language used be a factor?

    Tuesday, 26-Dec-17 18:55:16 UTC from gs.kawa-kun.com
  5. In at least five years of running SN/GS instances, I've always felt that # / # logs resemble #'s logging. Far too much info, but never enough about the actual problem you're investigating.

    Friday, 22-Dec-17 16:40:12 UTC from gs.kawa-kun.com
  6. In at least five years of running SN/GS instances, I've always felt that # / # logs resemble #'s logging. Far too much info, but never enough about the actual problem you're investigating.

    Friday, 01-Dec-17 11:55:10 UTC from gs.kawa-kun.com
  7. Now seen in context. Did you use # or # in your recent research presentation? Could the language used be a factor?

    Saturday, 11-Nov-17 13:25:10 UTC from gs.kawa-kun.com
  8. In at least five years of running SN/GS instances, I've always felt that # / # logs resemble #'s logging. Far too much info, but never enough about the actual problem you're investigating.

    Tuesday, 17-Oct-17 06:10:18 UTC from gs.kawa-kun.com
  9. Now seen in context. Did you use # or # in your recent research presentation? Could the language used be a factor?

    Tuesday, 03-Oct-17 19:55:12 UTC from gs.kawa-kun.com
  10. To anyone who works with # : Is # a meme?
    https://twitter.com/netbeans/status/913512033294995456

    Thursday, 28-Sep-17 23:52:36 UTC from gs.smuglo.li in context
  11. No, nothing that would be helpful. Current or former # product, targeted below #, above # Every time I see # mentioned, I also see # I've never seen it in use anywhere.

    Friday, 11-Aug-17 13:40:12 UTC from gs.kawa-kun.com
  12. Now seen in context. Did you use # or # in your recent research presentation? Could the language used be a factor?

    Sunday, 23-Jul-17 21:40:12 UTC from gs.kawa-kun.com
  13. Kind of seems like all the # stuff designed to reduce typing also makes Java harder to debug.

    Tuesday, 13-Jun-17 17:48:49 UTC from gs.kawa-kun.com
  14. Looks like there's a # parser for !Pythonhttps://github.com/c2nes/javalang

    This'll be useful for my job.

    Monday, 15-May-17 18:45:10 UTC from gs.kawa-kun.com in context Repeated by takeshitakenji
  15. Looks like there's a # parser for !Pythonhttps://github.com/c2nes/javalang

    This'll be useful for my job.

    Monday, 15-May-17 18:45:10 UTC from gs.kawa-kun.com in context
  16. Looks like there's a # parser for !Pythonhttps://github.com/c2nes/javalang

    This'll be useful for my job.

    Monday, 15-May-17 11:41:05 UTC from gs.kawa-kun.com in context Repeated by takeshitakenji
  17. Looks like there's a # parser for !Pythonhttps://github.com/c2nes/javalang

    This'll be useful for my job.

    Monday, 15-May-17 11:41:05 UTC from gs.kawa-kun.com in context
  18. Developing in

    #perl
    #c++ #cxx
    #java (android)
    #swift (sometimes)

    Trying to learn #haskell

    Also trying to avoid #javascript

    #developers of the fediverse, state your languages so we can connect!

    Monday, 17-Apr-17 13:49:26 UTC from mastodon.social Repeated by dtluna
  19. @littlefox
    I am pretty opinionated in my choices:
    # - hail our Gods K&R
    # - what I use at work and for scripts, very pleasant language
    # - I am helping to write the Pleroma backend in it

    Gave two chances to #, it has failed me, now I consider it a meme

    Hate # and # # is bearable, but I try to stay away.

    Monday, 17-Apr-17 14:14:44 UTC from social.heldscal.la
  20. Developing in

    #perl
    #c++ #cxx
    #java (android)
    #swift (sometimes)

    Trying to learn #haskell

    Also trying to avoid #javascript

    #developers of the fediverse, state your languages so we can connect!

    Monday, 17-Apr-17 13:49:26 UTC from mastodon.social
  21. https://batcaveposter.club/attachment/551007 # #

    Friday, 31-Mar-17 07:39:52 UTC from shitposter.club in context
  22. Now seen in context. Did you use # or # in your recent research presentation? Could the language used be a factor?

    Tuesday, 14-Mar-17 11:25:07 UTC from gs.kawa-kun.com
  23. Now seen in context. Did you use # or # in your recent research presentation? Could the language used be a factor?

    Wednesday, 08-Mar-17 22:10:17 UTC from gs.kawa-kun.com
  24. @dogjaw @takekiwiakenji @chen @kitredgrave JS has the same story. Was supposed to be Scheme for the browser, but it was designed in a time when the # hype train was still going, so it got that syntax.

    Saturday, 18-Feb-17 03:40:35 UTC from gs.archae.me
  25. In at least five years of running SN/GS instances, I've always felt that # / # logs resemble #'s logging. Far too much info, but never enough about the actual problem you're investigating.

    Friday, 17-Feb-17 18:40:07 UTC from gs.kawa-kun.com
  26. In at least five years of running SN/GS instances, I've always felt that # / # logs resemble #'s logging. Far too much info, but never enough about the actual problem you're investigating.

    Thursday, 02-Feb-17 16:25:11 UTC from gs.kawa-kun.com
  27. Mockito is weird. #

    Monday, 30-Jan-17 16:52:30 UTC from gs.kawa-kun.com
  28. @takemangoakenji In at least five years of running SN/GS instances, I've always felt that # / # logs resemble #'s logging. Far too much info, but never enough about the actual problem you're investigating.

    Sunday, 08-Jan-17 16:26:06 UTC from n2.federati.net in context Repeated by takeshitakenji
  29. @takemangoakenji In at least five years of running SN/GS instances, I've always felt that # / # logs resemble #'s logging. Far too much info, but never enough about the actual problem you're investigating.

    Sunday, 08-Jan-17 16:26:06 UTC from n2.federati.net in context
  30. Now seen in context. Did you use # or # in your recent research presentation? Could the language used be a factor?

    Monday, 19-Dec-16 11:55:06 UTC from gs.kawa-kun.com